503 for 45 minutes
Posted by eumelia in general.
Replies
That 503 means the panel couldn’t load the page; it doesn’t by itself mean your server is down. Since it’s lasted over 45 minutes: 1. Check https://wispbyte.com/status for updates, then try again in a few minutes. 2. If the server page loads, press Start once and copy the console output until it stops. If it continues, reply with your node name, support tag, and whether the console page loads. Remove any tokens or secrets from logs.
The support tag is e5b5a18d I cannot access the management to find the node name. The console does not load, thats where I get the server is busy message.
My console is not working too and i am also 0remium client
You should open a support ticket and get them to fix yours and tell them to check the forum for the rest of us.
Okay. So I think I have found the answer. I joined the discord and on there they put up an announcement today. The website will not be available for a short period of time. https://patchstack.com/articles/php major vulnerability alert 10 2026/ Our panels are written in PHP, until we apply a temporary patch / deploy the PHP update which is expected to be released at 14:00 UTC, Today, we will not provide access until the fix is there. Servers are not affected, they'll continue to run. Thank you for understanding! Patchstack Major security alert: PHP vulnerable to critical RCE, attacks ongoi... An attacker with valid UpdraftCentral dashboard keys is installing backdoors on connected WordPress sites. Delete your UpdraftCentral keys! Major security alert: PHP vulnerable to critical RCE, attacks ongoi... As we're getting closer and closer to the release of the update, there will be more people trying to exploit this vulnerability, we'd rather not risk anything and take in a short backend downtime.
"Our panels are written in PHP, until we apply a temporary patch / deploy the PHP update which is expected to be released at 14:00 UTC, Today, we will not provide access until the fix is there. Servers are not affected, they'll continue to run." 14:00UTC is 10AM EST, which was 45 minutes ago and servers are clearly not running. :')
The servers are still running. You just can't access the webpages for them. My bot is still running and usable, I just can't access the backend.