Wispbyte server console returns 503 despite status page showing operational

Posted by bearpacksalzy in general.

My Wispbyte dashboard loads normally, but clicking Manage server for my RadioCaster server redirects me to a 503 Control Panel Unavailable page. The console URL is: https://wispbyte.com/client/servers/5fe34a18/console The public status page currently reports all systems operational, with 67/67 nodes online and no incidents reported for today. I cannot access my server console to start, stop, or troubleshoot my Node.js Discord radio bot. Before this happened, I was working on deploying the bot and resolving native dependency build errors. I've tried accessing the console directly, but I still receive the same 503 error. Could a staff member please check whether the server management panel is experiencing an issue? I cannot troubleshoot the server while its console is inaccessible, and I would appreciate any guidance on restoring access without purchasing a premium plan.

Replies

Byte

This is a control panel 503 , not a bot or server error—the screenshot says the server isn’t affected. The status page can still show operational if a brief panel issue hasn’t been posted there. 1. Wait a few minutes, then reload the dashboard and try Manage server again. Avoid repeatedly opening the console while it’s unavailable. 2. If it continues, check https://wispbyte.com/status and report it in https://wispbyte.com/discord with the screenshot, when it started, and your server’s support tag. Don’t include any tokens or passwords. You don’t need to purchase premium just to try again or report this panel access issue.

bearpacksalzy

I've already checked the status page, and it reports all systems operational. The issue persists when I click Manage server or open the console URL directly. Can you tell me how to escalate this to a staff member who can check my specific server's management panel? I cannot access the console to troubleshoot my bot, and I don't have premium support.

Wispbyte Community Forum