HTTP 502 Error since update to Synology Calendar Version: 2.5.0-21145 #783
-
Dear Sirs, Apparently some changes were implemented. Other clients (i.e. Thunderbird) still work well. Therefore it is likely synology has implemented some changes leading to this error. Many thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
Hello, this seems to be a bug introduced with the latest updates on Synology. Please have a look here where it is already reported: https://community.synology.com/enu/forum/1/post/187744 Hope they can identify the cause of this and offer an update soon! |
Beta Was this translation helpful? Give feedback.
-
We've investigated a bit more: This error does not seem to be directly related to any VEVENT itself, but to an internal warning text from Synology that is put before the actual parsing code of the VEVENT. So the XML parser wants to start but there is no XML code to parse, instead it is a warning text before the XML. Thus it crashes. You can also try to somehow disable warning messages on Synology. Then it would not inject additional text before the actual XML and it should start working again. You could as an admin enable SSH for Synology in the DSM settings under "Terminal & SMNP" and then connect to it on a console. then disable it directly in
and on line at the end add &~E_WARNING like:
Can you try that? If that removes the error we have some proof that we can report to Synology. |
Beta Was this translation helpful? Give feedback.
-
It seems to be already being investigated by Synology as you can read here in the posting from May 8th: https://community.synology.com/enu/forum/1/post/187819 |
Beta Was this translation helpful? Give feedback.
-
Tried the same change in the same file. Also restarted Packages PHP 8.1, Calendar Package and Webstation Package... But I still got 502. But there is a Version 2.5.1-21153 available now - fixes the issue! (And also reverts the above change) |
Beta Was this translation helpful? Give feedback.
Hello,
this seems to be a bug introduced with the latest updates on Synology. Please have a look here where it is already reported: https://community.synology.com/enu/forum/1/post/187744
Hope they can identify the cause of this and offer an update soon!