When I try to add a new server, I get this error: “Error 503 first byte timeout”. I also get an error when using the “NTP Check”.

Hello @mclc , and welcome to the community! The backend systems have been migrated from one provider to another set of systems recently. The migration as such is complete , but there’s still some glitches here and there - the inability to add new servers being one of them. As he asked for feedback, …

Yeah, I’ve been doing a bunch of small fixes from fallouts to the changes in the new cluster. Adding servers (and the NTP Check) should work now.

I now receive a 403 when trying to add a new server request id 01KQ4W4X4BY00N1206EFR8TDCK, trace id 200986f17a07aa571e9623d163c203c2. NTP Check works.

And now we’re back to “Error 503 first byte timeout”

Adding new server

Server operators

ask April 29, 2026, 10:40am 6

@mclc should be fixed! See New Server Add issue - #6 by ask

Topic		Replies	Views
New Server Add issue Server operators monitoring	11	333	May 11, 2026
Still issues, or...? Server operators	13	428	May 11, 2026
Could not decode NTP response from trace server Uncategorized	6	608	August 5, 2023
Ntp pool beta: Could not check NTP status Server operators beta	3	1211	February 12, 2019
Can't re-add a server with its new IPv6 Server operators	8	729	April 10, 2024

Adding new server

Related topics