Webmin [Virtualmin] system reboot error when using Cloudflare

Webmin
1

I have noticed that when rebooting the system through webmin an error shows up in a bouncing red window at the bottom of the screen:

Error: 521 - error – /xhr.cgi?xhr-check=1

The system reboots OK and the webmin screen reactivates normally. This only occurs when using cloudflare and running webmin on port: 8443.

Is there any way to stop this happening?

Thanks

SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.5
Webmin version 2.202
2

I realise that this is only a cosmetic issue. But it makes Virtualmin look unprofessional and is difficult to explain to clients.

3

Off topic on your own topic.

1 Like
4

Yes, you should configure Cloudflare for the domain where Webmin is running to avoid interfering with requests. It’s likely that you’ve enabled advanced security settings and tightened them too much, causing things to break.

5

I am using the default Cloudflare settings. I will try disabling the standard security settings and see if it has any effect.

Thanks

6

Well, I’ve turned off all security (as much as possible ‘essentially off’ setting) and it still gives the disconnect error on reboot. Finally I disabled the Cloudlfare proxy on the host A record and made a rule to remove Cloudflare SSL on the host domain. So, this keeps cloudflare for everything else except Webmin / Virtualmin - which seems to work better.

7

Just to mention - I was also, occasionally, receiving the pop-up, red windowed, disconnection error message when using the file manager. With Cloudflare disabled this has also stopped.

8

You’re expecting a proxied connection to work like a not proxied connection and blaming us when it doesn’t. That’s not fair to Virtualmin.

9

I’m not blaming you. I’m not blaming anyone. I am very grateful to be able to use Virtualmin instead of Cpanel and am considering paid plans. I was just under the impression that Virtualmin worked the same with Cloudflare enabled as long as you changed the port. Thanks to the good advice here I was able to find a workaround.

10

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.