The error described at https://sourceforge.net/p/webadmin/bugs/5059/ still seems to exist (in some form) in 1.890. (I opened a new ticket to indicate the Milestone to which the bug applied, rather than commenting on the old one. Please accept my apologies if that was incorrect.)
The symptoms are almost exactly the same in that the modal pops up indicating that the connection was lost:
https://www.dropbox.com/s/zvvqzo4oxwsppfb/Screenshot%202018-09-06%2009.50.46.png?raw=1
The difference is that it's not happening every 30 seconds, but rather while clicking around (and especially if I click another link while the previous click is still processing). We're seeing this on a variety of servers, all running CentOS 6 or 7, but all with background status collection turned on (with intervals set between 5 and 3660 minutes; it doesn't seem to make any difference). Further, it more often happens on servers with a higher load, presumably because the Webmin service is struggling to complete one request when another one is submitted. The problem is that it's not always obvious when it's still working a request in the background or whatnot, especially stuff like the incredibly CPU-intensive stats.cgi or other bits of Authentic.
Which browser are you using there? If it's chrome or some other that has a network debug console, I'd be interested to see what HTTP requests are failing when you get that error..
I'm using Chrome, and here's a couple of typical screenshots of the problem:
https://www.dropbox.com/s/q3ysd1vm70phk8l/Screenshot%202018-09-25%2015.35.12.png?raw=1
https://www.dropbox.com/s/tc6wumrpqh2l3z5/Screenshot%202018-09-25%2015.35.31.png?raw=1
The second one I took after maybe 10–15 seconds of doing nothing. I triggered the problem by clicking around a bit faster than the requests could be serviced.
I hope that's in any way helpful!
I will give it a test with throttled networks tomorrow, and come back to you a bit later.
Thanks.
Okay, great point. There was a design flaw on one of the subroutines in the theme. It's fixed and will be added to the upcoming 19.20 theme release. In case you want to check it now, go ahead and force update to the latest development version using theme configuration.
Thanks a lot for pointing this out. :)
It's our pleasure - thanks for a great product and a quick fix. :-D