ropg / ezTime

Is there some error with the server?
It doesn't respond to requests since around 10:30 Stockholm time?

Is there some error with the server? It doesn't respond to requests since around 10:30 Stockholm time?

Correct, I'm upgrading... Sorry for the disruption...

Ok!
Thank you for the superquick response!
When do you think it will be up again?
Best regards, Anders

Thank you for the superquick response! When do you yhink it will be up again?

It's up again.

Supermany thanks!
Best regards, Anders

ezTime/src/ezTime.h

Lines 153 to 155 in 7b3c8aa

    
           #define TIMEZONED_REMOTE_HOST	"timezoned.rop.nl" 
        
           #define TIMEZONED_REMOTE_PORT	2342 
        
           #define TIMEZONED_LOCAL_PORT	2342

I can't get connection on the port 2342. But it was success on the port 2343.
Could you return 2342, please? It's necessary for my devices.
Thank you in advance!

@ropg can't resolve timezones anymore, so did your upgrade break stuff?

[21:51:50][ 13976| 12440] updateSettin( 163): -> field[ntptimezone], newValue[CET]
[21:51:52][ 13304| 12440] startNTP ( 151): Error setting Timezone: Timeout
[21:51:52][ 11960| 11144] startNTP ( 169): UTC time : Thursday, 16-Sep-2021 21:51:52 UTC
[21:51:52][ 11960| 11144] startNTP ( 170): local time: Thursday, 16-Sep-2021 21:51:52 UTC

The server retreive of TZ location fails...

Hello, The server retrieve of TZ location fails, no connection to UDP 2342

Hi!
Do you have any update of what has happened and when it will work again?
Best regards,
Anders

Hello, The server is currently not responding - do you know when it will be available again?
Thanks in advance.

FWIW #123 makes setting a custom server easier.

Holy crap, the 2343 was a mistake on my end, and then I didn't check my computer again. I'm so, so sorry...

it should now be up at 2342. Please test.

Sorry...

(And yes, I think it would make sense to have a service like timezoned have more servers, but it's my own homebrew protocol instead of something standardized that has an RFC and all. Will work on putting it on the same box that hosts my backup nameserver so there's at least two.)

The port is still not open...

Now server is responding with timezone definition on port 2342 so it seems ok!
Thanks!

The port is still not open...

You can´t scan UDP! Because it´s a connectionless protocol.

To check if it's working, use:

$ nc -u timezoned.rop.nl 2342

And then type any identifier and follow it with a Ctrl-D (and no return). You'll then see the timezone info right after what you typed:

londonOK Europe/London GMT0BST,M3.5.0/1,M10.5.0

@ropg
And yes, I think it would make sense to have a service like timezoned have more servers

Did a crude attempt here, putting your code in a container image.

https://github.com/TheGroundZero/ezTimeContainer

	#define TIMEZONED_REMOTE_HOST "timezoned.rop.nl"
	#define TIMEZONED_REMOTE_PORT 2342
	#define TIMEZONED_LOCAL_PORT 2342

Is timeserver not responding?