Server Restart Fails with CDN Proxy & KeyError on Blocked IP List (Beta Version)

jaehyun1122

Hello,

I’d like to report two bugs found while using aaPanel. They are reproducible under specific conditions and affect either both versions or the beta only.

⸻

Server Restart Fails When Using Cloudflare Proxy (Stable & Beta)

Description:
Clicking the “Server Restart” button on the Home page fails if the panel is behind a Cloudflare proxy. The browser shows 520 or 521 errors, which are returned by Cloudflare. The restart only works after disabling the proxy.

This behavior occurs in both stable and beta versions, making it a consistent issue when using CDN services like Cloudflare.

KeyError When Viewing Blocked IP Addresses (Beta Only)

Description:
When navigating to Brute Force Protection > Blocked IP Addresses in the beta version, a KeyError related to the missing field logintime appears, and the list fails to load.

At first, I assumed this was an issue only on my main server. However, I’ve confirmed that it also occurs on a fresh new instance using the same beta version.
This error does not occur in the stable release.

Thank you for your continued development of aaPanel!

aaPanel_Kern

Hello,
Thank you for your feedback,

The current restart of filtering is not done well. After the panel program is successfully started, refresh it.
We will fix it

jaehyun1122

aaPanel_Kern

Hello again,

After further testing, I’ve identified the real cause of the issue. The panel restart functionality fails completely when accessed through a CDN or reverse proxy.

When the proxy is disabled, the restart API request (e.g., system?action=RestartServer) returns HTTP 200 OK, and everything works as expected.

However, when the proxy is enabled, the same API requests fail with HTTP 521, which means the origin server is unreachable from the proxy.

As a result, no server or panel restart actually happens the API doesn’t go through, and the user sees no effect at all.

Thanks again for your support.

jaehyun1122

aaPanel_Kern

Hi, just following up to see if there’s any update on this issue. Let me know if any further information is needed!

aaPanel_Kern

Hello,
Isn't this normal situation?
You will naturally not be able to access the panel normally after restarting it.
CloudFlare will display 521, and it will automatically recover after the panel is restarted.
jaehyun1122

jaehyun1122

aaPanel_Kern

Hello,
To clearly demonstrate the issue, I’ve created a new instance where the problem can be reproduced. I will send the relevant access information via email so you can check it directly.
Please let me know if you need anything else or if you have any feedback after checking.

Thank you.