Unable to access VirtualMin dashboard through Hostname

I did try and post this earlier, but I think it got deleted

SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.1
Virtualmin version 7.3-1

Hello Awesome Virtualmin Peeps,

I’ve recently setup a Virtualmin server on my home network for running some WordPress websites and some mailboxes.

The setup went really well. I can access the boxes web interface just fine using the local network address +port number with no issues. But when trying to access the Virtualmin dashboard using its configured hostname+port ms2-virtualmin.wpfreelancer.co.uk:10000, I’m having issues with the page hanging. The Virtualmin logo and spinner appear briefly, but the page doesn’t load

image

I believe this is a DNS configuration issue but I’m not sure where I’m going wrong.

I’ve set the system hostname to ms2-virtualmin.wpfreelancer.co.uk and added A pointer record in my DNS to the IP address which has propagated.

image

Looking at the browser debugging tools I’m seeing NS_BINDING_ABORTED on some of the network traffic which I assume is being caused by DNS misconfiguration.

I’ve setup a Virtual server for ms2-virtualmin.wpfreelancer.co.uk and issued an SSL cert with Let’s Encrypt. I’m not using Virtualmin for DNS management, at the moment. For this DNS zone, the following nameservers have been setup, I’m using ‘Google Domains’ registar and I’m looking to copy and manage any necessary DNS configuration via Google Domains dashboard so I can learn more about DNS and what is necessary and what isn’t. The nameservers for this zone have been set to

Any ideas or pointers to investigate would be great. Many thanks.

Welcome to Virtualmin

Just following that url I see your Wordpress default page and it appears stable.

The only issue I see is no SSL. Are you sure you have a Lets Encrypt SSL ? Check Server Configuration -> SSL Certificate

I also get the Webmin default login page with your url:10000 so everything lookhs good from here

Thanks for your reply Stegan. The SSL Certificate is applied correctly and is coming up on the browser. And like you say the login page is loading correctly as well, but after login the Virtualmin dashboard doesn’t load, see this quick video of that behaviour:

That one has me beat I’m afraid. This may be a stupid suggestion but have you tried clearing cache? Have you also tried login using the IP address + port. 80.229.15.223:10000

I know this is a separate issue but do you see the WP site with SSL padlock because it is still http only for me.

Perhaps I need to bow out to @staff who will have better understanding, good luck

No worries thanks for having a look.

Just tried 80.229.15.223:10000 and again I can log in but the dashboard hangs on loading the same as loading ms2-virtualmin.wpfreelancer.co.uk:10000.

There is no WordPress site associated with http://wpfreelancer.co.uk/ it’s showing the site hefin.co.uk. There is a setting in VirtualMin to show a default site if no site currently exists I think that’s what happening there. Thanks again @Stegan like you say hopefully, @staff might take a gander at this and might have an idea what’s going on.

Don’t combine problems. I can’t quickly see what’s happening here, as there’s discussion of WordPress, default site, and Virtualmin login. Please focus! One problem per topic, so I can drop in and figure out what I’m trying to solve quickly.

I’m gonna pick the Virtualmin problem to talk about, since that’s what’s in the title, and ask you split other problems/questions into their own topic with a reasonable title. (Also see forum guidelines.)

NS_BINDING_ABORTED indicates the request load was canceled, and it seems like it can show up in redirects: Re: NS_BINDING_ABORTED - Boris Zbarsky - org.mozilla.lists.dev-tech-xpcom - MarkMail

I don’t think it indicates a name server problem.

We sometimes see weird issues like this when folks have configured Webmin to run behind a proxy, but that doesn’t seem to be what’s happening here, at least not intentionally.

Have you tried a different browser, one without any extensions enabled? Also try a different network, if you can.

How’s memory? It’s plausible (though I haven’t seen it) that some background processes might get killed by the OOM killer, which would prevent them from ever sending data back…the dashboard is relatively heavy, as it’s pulling data from a bunch of different sources. It’s mostly cached, but it’s still going to spawn more processes than almost any other page in Webmin/Virtualmin.

Oh, and yes, we need to see the log! Probably miniserv.error in this case, which is in /var/webmin

Hey @Joe

Here’s the contents of /var/webmin/miniserv.error

[09/Dec/2022:13:43:08 +0000] miniserv.pl started
[09/Dec/2022:13:43:08 +0000] IPv6 support cannot be enabled without the Socket6 perl module
[09/Dec/2022:13:43:08 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:13:43:08 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:13:43:08 +0000] PAM authentication enabled
[09/Dec/2022:13:43:32 +0000] Reloading configuration
[09/Dec/2022:13:43:33 +0000] Reloading configuration
[09/Dec/2022:13:43:34 +0000] Reloading configuration
[09/Dec/2022:13:43:35 +0000] Reloading configuration
[09/Dec/2022:13:47:42 +0000] Shutting down
[09/Dec/2022:13:47:44 +0000] miniserv.pl started
[09/Dec/2022:13:47:44 +0000] IPv6 support enabled
[09/Dec/2022:13:47:44 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:13:47:44 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:13:47:44 +0000] PAM authentication enabled
[09/Dec/2022:13:51:38 +0000] Reloading configuration
[09/Dec/2022:13:51:55 +0000] Reloading configuration
[09/Dec/2022:14:25:47 +0000] Restarting
[09/Dec/2022:14:25:50 +0000] miniserv.pl started
[09/Dec/2022:14:25:50 +0000] IPv6 support enabled
[09/Dec/2022:14:25:50 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:14:25:50 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:14:25:50 +0000] PAM authentication enabled
[09/Dec/2022:14:35:55 +0000] Reloading configuration
[09/Dec/2022:14:36:13 +0000] Reloading configuration
[09/Dec/2022:14:36:43 +0000] Restarting
[09/Dec/2022:14:36:46 +0000] miniserv.pl started
[09/Dec/2022:14:36:46 +0000] IPv6 support enabled
[09/Dec/2022:14:36:46 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:14:36:46 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:14:36:46 +0000] PAM authentication enabled
[09/Dec/2022:14:36:58 +0000] Reloading configuration
[09/Dec/2022:14:40:59 +0000] Reloading configuration
Error: Missing or invalid database name - only letters, numbers and _ are allowed
[09/Dec/2022:14:41:58 +0000] Reloading configuration
[09/Dec/2022:14:44:13 +0000] Reloading configuration
[09/Dec/2022:14:44:40 +0000] Reloading configuration
Error: None selected
[09/Dec/2022:14:53:54 +0000] Reloading configuration
[09/Dec/2022:15:15:21 +0000] Reloading configuration
Error: SQL create user 'hefin_co_uk_db_usr'@'localhost' identified  by 'Vhb9J9idUrWt' failed : Operation CREATE USER failed for 'hefin_co_uk_db_usr'@'localhost'
Error: SQL create user 'hefin_co_uk_db_usr'@'localhost' identified  by 'Vhb9J9idUrWt' failed : Operation CREATE USER failed for 'hefin_co_uk_db_usr'@'localhost'
Error: SQL create user 'hefin_co_uk_db_usr'@'localhost' identified  by 'Vhb9J9idUrWt' failed : Operation CREATE USER failed for 'hefin_co_uk_db_usr'@'localhost'
Error: SQL alter user 'hefin_co_uk_db_user'@'' with max_user_connections 0 failed : Operation ALTER USER failed for 'hefin_co_uk_db_user'@'%'
Error: SQL create user 'hefin_co_uk_db_usr'@'localhost' identified  by '2gMq3GOICIlPuT4' failed : Operation CREATE USER failed for 'hefin_co_uk_db_usr'@'localhost'
Error: SQL rename user 'hefin_co_uk_db_usr'@'%' to 'hefin_co_uk_db_usr'@'localhost' failed : Operation RENAME USER failed for 'hefin_co_uk_db_usr'@'%'
Error: SQL rename user 'hefin_co_uk_db_usr'@'%' to 'hefin_co_uk_db_usr'@'localhost' failed : Operation RENAME USER failed for 'hefin_co_uk_db_usr'@'%'
Error: SQL rename user 'hefin_co_uk_db_usr'@'%' to 'hefin_co_uk_db_usr'@'@' failed : Malformed hostname (illegal symbol: '@')
Error: SQL rename user 'hefin_co_uk_db_usr'@'localhos' to 'hefin_co_uk_db_usr'@'localhost' failed : Operation RENAME USER failed for 'hefin_co_uk_db_usr'@'localhos'
[09/Dec/2022:17:26:48 +0000] Reloading configuration
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
[09/Dec/2022:17:38:25 +0000] [192.168.1.1] Timeout : Waited for 350 seconds for start of headers
[09/Dec/2022:17:38:35 +0000] [192.168.1.1] Timeout : Waited for 360 seconds for start of headers
[09/Dec/2022:17:38:55 +0000] [192.168.1.1] Timeout : Waited for 310 seconds for start of headers
[09/Dec/2022:17:38:59 +0000] [192.168.1.1] Timeout : Waited for 310 seconds for start of headers
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
Too many connections (26) from IP 192.168.1.1
[09/Dec/2022:17:39:05 +0000] [192.168.1.1] Timeout : Waited for 390 seconds for start of headers
[09/Dec/2022:17:39:05 +0000] [192.168.1.1] Timeout : Waited for 320 seconds for start of headers
[09/Dec/2022:17:39:08 +0000] [192.168.1.1] Timeout : Waited for 320 seconds for start of headers
[09/Dec/2022:17:39:15 +0000] [192.168.1.1] Timeout : Waited for 330 seconds for start of headers
[09/Dec/2022:17:39:25 +0000] [192.168.1.1] Timeout : Waited for 410 seconds for start of headers
[09/Dec/2022:17:39:25 +0000] [192.168.1.1] Timeout : Waited for 340 seconds for start of headers
[09/Dec/2022:17:39:26 +0000] [192.168.1.1] Timeout : Waited for 450 seconds for start of headers
[09/Dec/2022:17:39:35 +0000] [192.168.1.1] Timeout : Waited for 420 seconds for start of headers
[09/Dec/2022:17:39:35 +0000] [192.168.1.1] Timeout : Waited for 350 seconds for start of headers
[09/Dec/2022:17:39:45 +0000] [192.168.1.1] Timeout : Waited for 430 seconds for start of headers
[09/Dec/2022:17:39:45 +0000] [192.168.1.1] Timeout : Waited for 360 seconds for start of headers
Error: Validation failed : DNS zone does not have any NS records
[09/Dec/2022:17:39:55 +0000] [192.168.1.1] Timeout : Waited for 370 seconds for start of headers
[09/Dec/2022:17:39:55 +0000] [192.168.1.1] Timeout : Waited for 440 seconds for start of headers
[09/Dec/2022:17:40:05 +0000] [192.168.1.1] Timeout : Waited for 450 seconds for start of headers
[09/Dec/2022:17:40:06 +0000] [192.168.1.1] Timeout : Waited for 490 seconds for start of headers
[09/Dec/2022:17:40:16 +0000] [192.168.1.1] Timeout : Waited for 500 seconds for start of headers
[09/Dec/2022:17:40:26 +0000] [192.168.1.1] Timeout : Waited for 510 seconds for start of headers
[09/Dec/2022:17:40:36 +0000] [192.168.1.1] Timeout : Waited for 520 seconds for start of headers
[09/Dec/2022:17:40:46 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[09/Dec/2022:17:40:52 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[09/Dec/2022:17:41:02 +0000] [192.168.1.1] Timeout : Waited for 550 seconds for start of headers
[09/Dec/2022:17:43:51 +0000] [192.168.1.1] Timeout : Waited for 290 seconds for start of headers
[09/Dec/2022:17:44:20 +0000] [192.168.1.1] Timeout : Waited for 320 seconds for start of headers
[09/Dec/2022:17:44:40 +0000] [192.168.1.1] Timeout : Waited for 340 seconds for start of headers
Use of uninitialized value $username in string eq at /usr/share/webmin/virtualmin-htpasswd/virtual_feature.pl line 245.
Error: Missing administration password
[09/Dec/2022:18:03:59 +0000] Reloading configuration
[09/Dec/2022:18:04:40 +0000] Restarting
[09/Dec/2022:18:04:43 +0000] miniserv.pl started
[09/Dec/2022:18:04:43 +0000] IPv6 support enabled
[09/Dec/2022:18:04:43 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:18:04:43 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:18:04:43 +0000] PAM authentication enabled
[09/Dec/2022:18:10:31 +0000] [192.168.1.1] Timeout : Waited for 450 seconds for start of headers
[09/Dec/2022:18:10:41 +0000] [192.168.1.1] Timeout : Waited for 460 seconds for start of headers
[09/Dec/2022:18:10:51 +0000] [192.168.1.1] Timeout : Waited for 470 seconds for start of headers
[09/Dec/2022:18:11:01 +0000] [192.168.1.1] Timeout : Waited for 480 seconds for start of headers
[09/Dec/2022:18:11:21 +0000] [192.168.1.1] Timeout : Waited for 500 seconds for start of headers
[09/Dec/2022:18:11:30 +0000] [192.168.1.1] Timeout : Waited for 510 seconds for start of headers
[09/Dec/2022:18:11:50 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[09/Dec/2022:18:14:46 +0000] Shutting down
[09/Dec/2022:18:15:48 +0000] miniserv.pl started
[09/Dec/2022:18:15:48 +0000] IPv6 support enabled
[09/Dec/2022:18:15:48 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:18:15:48 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:18:15:48 +0000] PAM authentication enabled
[09/Dec/2022:18:16:06 +0000] Shutting down
[09/Dec/2022:18:18:51 +0000] miniserv.pl started
[09/Dec/2022:18:18:51 +0000] IPv6 support enabled
[09/Dec/2022:18:18:51 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:18:18:51 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:18:18:51 +0000] PAM authentication enabled
[09/Dec/2022:18:23:04 +0000] miniserv.pl started
[09/Dec/2022:18:23:04 +0000] IPv6 support enabled
[09/Dec/2022:18:23:04 +0000] Using MD5 module Digest::MD5
[09/Dec/2022:18:23:04 +0000] Using SHA512 module Crypt::SHA
[09/Dec/2022:18:23:04 +0000] PAM authentication enabled
[09/Dec/2022:19:30:16 +0000] Reloading configuration
Use of uninitialized value $username in string eq at /usr/share/webmin/virtualmin-htpasswd/virtual_feature.pl line 245.
[09/Dec/2022:21:38:37 +0000] [192.168.1.1] Timeout : Waited for 480 seconds for start of headers
[09/Dec/2022:21:38:47 +0000] [192.168.1.1] Timeout : Waited for 490 seconds for start of headers
[09/Dec/2022:21:38:57 +0000] [192.168.1.1] Timeout : Waited for 500 seconds for start of headers
[09/Dec/2022:21:39:07 +0000] [192.168.1.1] Timeout : Waited for 510 seconds for start of headers
[09/Dec/2022:21:40:38 +0000] [192.168.1.1] Timeout : Waited for 480 seconds for start of headers
[09/Dec/2022:21:40:48 +0000] [192.168.1.1] Timeout : Waited for 490 seconds for start of headers
[09/Dec/2022:21:40:58 +0000] [192.168.1.1] Timeout : Waited for 500 seconds for start of headers
[10/Dec/2022:15:52:29 +0000] [192.168.1.1] Timeout : Waited for 430 seconds for start of headers
[10/Dec/2022:17:15:19 +0000] Reloading configuration
[10/Dec/2022:17:16:15 +0000] Reloading configuration
[10/Dec/2022:17:53:03 +0000] [192.168.1.1] Timeout : Waited for 420 seconds for start of headers
[10/Dec/2022:17:53:03 +0000] [192.168.1.1] Timeout : Waited for 420 seconds for start of headers
[10/Dec/2022:17:53:13 +0000] [192.168.1.1] Timeout : Waited for 430 seconds for start of headers
[10/Dec/2022:17:53:19 +0000] [192.168.1.1] Timeout : Waited for 450 seconds for start of headers
[10/Dec/2022:17:53:23 +0000] [192.168.1.1] Timeout : Waited for 440 seconds for start of headers
[10/Dec/2022:17:53:59 +0000] [192.168.1.1] Timeout : Waited for 490 seconds for start of headers
[10/Dec/2022:17:54:08 +0000] [192.168.1.1] Timeout : Waited for 500 seconds for start of headers
[10/Dec/2022:17:54:18 +0000] [192.168.1.1] Timeout : Waited for 510 seconds for start of headers
[10/Dec/2022:17:54:28 +0000] [192.168.1.1] Timeout : Waited for 520 seconds for start of headers
[10/Dec/2022:17:54:38 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[10/Dec/2022:17:54:46 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:17:54:56 +0000] [192.168.1.1] Timeout : Waited for 550 seconds for start of headers
[10/Dec/2022:18:28:09 +0000] [192.168.1.1] Timeout : Waited for 520 seconds for start of headers
[10/Dec/2022:18:28:13 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[10/Dec/2022:18:28:23 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:18:33:20 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[10/Dec/2022:18:38:41 +0000] [192.168.1.1] Timeout : Waited for 550 seconds for start of headers
[10/Dec/2022:18:44:01 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:18:50:01 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:19:01:35 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[10/Dec/2022:19:01:45 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:19:06:45 +0000] [192.168.1.1] Timeout : Waited for 530 seconds for start of headers
[10/Dec/2022:19:11:57 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:19:17:26 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers
[10/Dec/2022:19:23:26 +0000] [192.168.1.1] Timeout : Waited for 540 seconds for start of headers

Sorry didn’t mention the server is behind a pfSense box, port number 10000 is forwarded to the local IP of the server.

The box is beefy Ram 16 GB on board and 2.5 GB in use. 6 core processor with tons of HD space. With nothing currently running apart from a default WordPress site (hefin.co.uk).
image

Tried Edge, Brave, firefox and chrome all exhibit the same issue. Attempted login via another machine same thing.

@Hefin, have you installed latest Authentic Theme 20.11 on Webmin 2.001? That would break things if so, and you will have to downgrade the theme or simply re-install (using package manager reinstall command) Webmin 2.001.

You can check what Webmin modules are installed by running webmin --versions command.

I ran ‘webmin --versions’

Webmin: 2.001 [/usr/share/webmin]
  Themes:
    Authentic Theme: 20.01.1 [authentic-theme]
  Modules:
    AWStats Reporting: 6.0 [virtualmin-awstats]
    Ruby GEMS: 1.9 [ruby-gems]
    Virtualmin Protected Directories: 3.1 [virtualmin-htpasswd]
    Virtualmin Virtual Servers: 7.3.gpl-1 [virtual-server]
Usermin: 1.860 [/usr/share/usermin]
  Themes:
    Authentic Theme: 20.00 [authentic-theme]

I’m running Authentic Theme: 20.01.1 so that’s bad? Don’t remember specifically opting in to that. Trying to keep things stock as much as possible to avoid issues. How would I downgrade the theme?

Would I use the Webmin UI theme radio buttons list and select the ‘Legacy Theme’?

image

Oh God no! My EYES!!! Legacy theme is circa 2001…for the love of all things holy, how do I get back?

Praise the lord found a way back the good light of the Authentic Theme the Legacy Theme is something else.

1 Like

You wouldn’t as you didn’t upgrade the theme (which is good, as the theme update will come with Webmin).

Oh God no! My EYES!!! Legacy theme is circa 2001…for the love of all things holy, how do I get back?

What, you really don’t like it? :smiley: I just recently had a request from a guy asking to help to switch back to the Legacy Theme (what you’re seeing right now).

There are two ways. Try both. First change it globally in Webmin / Webmin configuration page and second try setting it for the given user in Webmin / Change Language and Theme page.

Praise the lord found a way back the good light of the Authentic Theme the Legacy Theme is something else.

The Lord has other things to do. There is no magic here. It can be easily fixed (most of the times easily).

1 Like

That guy is some OG time lord! I had to rub bleach in my eyes! Well it wasn’t that bad, but…

So I’m going to Webmin / Webmin configuration / Usermin Themes

Changed it to Gray Framed Theme right?

Then in Webmin / Change Language and Theme I choose Gray Framed Theme again?

I get this interface

Which compared to the legacy theme is like something off the Starship Enterprise.

Still same login issue though :sweat_smile:

I have no clue off hand what’s wrong. But I could login tomorrow to your system and have a closer look. You could PM me credentials if that’s an accessible from the outside system.

Although, if you can access your system using an IP address, and cannot using a hostname it means there is a DNS problem. You can use dnschecker.org to try to figure out what’s wrong.

You can SSH in to that box with my IP if that’s a help?

Just FYI: If you search for pfsense on this forum, that type of issue has happened with those particular brand boxes before. Several times.

Thanks @Gomez_Adams I’ll do some searching.