Help with Docker install: Clock/Timers not working

[lukestein]

Hi team. I'm sorry for being very incompetent with Docker, but I have successfully set up a number of other simple docker projects on my Synology NAS and for some reason I'm struggling with ontime. Any ideas appreciated.

The key problem I'm facing is that after deploying the container, while I can access and interact with Ontime via local URL, its clock always shows "00:00:00" and timers won't run, as if no time data is making it's way into the container.

I installed using Synology DSM Container Manager, which has worked fine for me with other containers. I have tried to mess with no settings other than adding the volume mount, adding the TZ environmental variable, and changing the outward-facing ports from 8888/9999.

Any advice would be very much appreciated!!

[alex-Arc]

Hey @lukestein could you pull up the developer console in you browser (in chrome by pressing F12)
if you go to the network tab, filter by WS and reload then reload, you should see clock data coming in

[lukestein]

Thank you for this suggestion! The console showed that the websockets were all failing.

It turns out that the Synology reverse proxy apparently blocks websockets by default. My friend K. pointed me towards this link which suggested a fix that fixed this problem in about 5 seconds. Thank you!!!

[cpvalente]

Hi @lukestein,

Thank you for reaching out and for the very detailed issue.

The runtime data (eg. timers) are distributed over websockets to the interface. The issue you describe is consistent with a failure of the server to deliver the websocket data to the UI.

We know that in some setups like NGINX you will need to configure a passthrough to websockets
From a quick search it seems that you may have to configure this in synology as well?
(first hit on google, not sure if up to date)

This issue comes up often enough that we need to add some documentation to clarify this behaviour

Hope this heps, otherwise please follow up and we can try and help you find a solution

EDIT: just realised that, by the time I have posted this, you had figure it out. Sorry about the late reply

[lukestein]

The idea that you have anything to apologize for here is crazy… you're providing free software and timely help. Thank YOU!

If this does come up regularly, may be worth adding something to the docs (not necessarily about Synology, but maybe some troubleshooting advice on the Docker page about checking websockets) just so that anyone stuck like I was and inexpert like I am has an idea what to google.