cannot access my original Webmin/Virtualmin dashboard server3.foo.com.au after creating a new virtual server foo.com.au

4 posts / 0 new
Last post
#1 Wed, 10/04/2017 - 19:29
adamjedgar

cannot access my original Webmin/Virtualmin dashboard server3.foo.com.au after creating a new virtual server foo.com.au

hi guys,

(foo.com.au is my domain name)

server3.foo.com.au is my original Google Cloud Debian hostname FQDN. Virtualmin was installed to this hostname fqdn.

foo.com.au is the new virtualmin virtual server i just created on the above instance

have i made a bad mistake in doing this???

My original virtualmin install system hostname is server3.foo.com.au (internal ip address 10.152.0.4)

I setup my whmcs.foo.com.au virtual server, and have that working. I should mention that i am having problems with the whmcs.foo.com.au Letsencrypt SSL certificate installation, it is still not completely resolved, i have successfully downloaded certificate through virtualmin but i still get browser invalid certificate error...so its still using my self signed one)

I decided to create my parent website for webhosting on a new virtualmin virtual server. So i have created a new virtual server called foo.com.au.

My registrar zone records are as follows

foo.com.au. A 3600 35.189.17.97 Remove / Update
mail A 3600 35.189.17.97 Remove / Update
mail.whmcs A 3600 35.189.17.97 Remove / Update
server3 A 3600 35.189.17.97 Remove / Update
whmcs A 3600 35.189.17.97 Remove / Update
www.whmcs CNAME 3600 whmcs.foo.com.au. Remove / Update
goannawebhosting.com.au. MX 3600 mail.foo.com.au. 5 Remove / Update
whmcs MX 3600 mail.whmcs.foo.com.au. 5 Remove / Update
foo.cm.au. NS 3600 ns1.partnerconsole.net. Remove / Update
foo.com.au. NS 3600 ns2.partnerconsole.net. Remove / Update
foo.com.au. NS 3600 ns3.partnerconsole.net. Remove / Update
foo.com.au. TXT 3600 "v=spf1 a mx a:foo.com.au ip4:10.152.0.4 ip4:35.189.17.97 ?all" Remove / Update
whmcs TXT 3600 "v=spf1 a mx a:whmcs.foo.com.au ip4:10.152.0.4 ip4:35.189.17.97 ?all"

As soon as i completed the creation of new virtual server foo.com.au , my access to my original virtualmin/webmin control panel at https://server3.foo.com.au:10000 has completely shit itself. I now see a web browser invalid SSL certificate authority error (so i assume its reverting back to my self signed one on the server?), and the Webmin/Virtualmin dashboard is nothing more than a blank grey screen that appears to be stuck in some kind of loop???

I can see the package updates Bell and can click on it, but that is all (everything else is completely blank). I have root access to dashboard interfaces for my virtual servers (whmcs.foo.com.au and foo.com.au) without any problems i just cannot access server3.foo.com.au dashboard.

What have i done wrong? How do i fix this?

(is this because my original install is a subdomain and i have now added the parent domain as a virtualmin virtual server under this subdomain Webmin Server? (I hope you understand what i mean)

If i delete the new virtual server "foo.com.au" that i just created, will my problem be resolved or is it too late and that would only make things worse?

Wed, 10/04/2017 - 20:15
Joe
Joe's picture

You're chasing a red herring. Domain names and subdomain names have no significance beyond being just names. They're all just names and can be completely independent of each other, up to and including possibly having their own zones in the BIND configuration. Webmin doesn't care what name it lives on, and neither does Apache.

I'm guessing you've got misconfigured or missing DNS records or host records but that's just guessing. It looks like Webmin is responding appropriately on that IP address. Maybe try just reloading the page a couple times. It's possible to have corrupted data in the browser cache.

Virtualmin creates a new zone for each new virtual server, by default. If you've recently pointed your glue records to the Virtualmin server but didn't add a record for the Webmin subdomain, that's all the explanation we need.

Check to be sure the system hostname is resolvable from your client (i.e. you can lookup the name locally and it returns the IP address of your server). But, really, you should be able to connect to Webmin on any name that resolves to your server IP address. Webmin doesn't care about names and the only place where names matter is in TLS certificates. You can use the parent domain name to connect to Webmin, you can use the original name you used, you can use a random name you add to your hosts file that points to that IP, or you can use the name of any Virtualmin-created domain (as long as it resolves to the server IP). Webmin does not care about names (your browser does for validating the cert, but that's it).

To be clear:

(is this because my original install is a subdomain and i have now added the parent domain as a virtualmin virtual server under this subdomain Webmin Server? (I hope you understand what i mean)

No. It definitely is not. As long as you've got a record for the subdomain in your new zone that resolves to the server IP, you can use any names you want. The name for the Webmin server just needs to resolve to the right IP; it does not care what the name is.

If i delete the new virtual server "foo.com.au" that i just created, will my problem be resolved or is it too late and that would only make things worse?

Almost certainly not. It might unbreak DNS, if you've got conflicting zones configured. But, the right solution to that is to fix your zone records. Make sure that original domain is resolvable from your client.

All that said, I just went through and tried all of the relevant names and I was able to connect to all of them on port 10000 (couldn't login, obviously, but Webmin is there).

Oh...is it possible you're running out of memory? A silently crashing Webmin would look like pages random failing to load.

Check dmesg for out of memory errors.

--

Check out the forum guidelines!

Wed, 10/04/2017 - 21:56
adamjedgar

You mention SSL...i am now getting the following on web browser when trying to access server3.foo.com.au

server3.foo.com.au (for example, passwords, messages or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID

i wasnt getting this before this happened.

Also, my google cloud monitoring is showing very low resource usage...so im hoping that memory is not the problem.

I might just delete the virtual server and see what happens.

Wooohooo! Joe you are a genius...it was my web browser data causing the problem. I cleared the cache and voila problem solved! Thank you much appreciated.

Now the only issue is, my recently installed letsencrypt SSL certificate isnt working at all...it was working prior to this all going pearshaped!

I am not sure how to get rid of all existing certificates and start a fresh with SSL?

AJECreative is the home of $5 webhosting, $15/month VPS servers (1cpu,1gb RAM, 25GB storage)
Centos7, Debian9, or Ubuntu18LTS
Available Control Panels = Centos-Webpanel, Cyberpanel, or Virtualmin

https://ajecreative.com.au

Wed, 10/04/2017 - 22:50 (Reply to #3)
Joe
Joe's picture

Any time you request a new certificate it replaces the old one.

Where are you seeing the certificate error? (I mean, in Webmin or on a website managed by Virtualmin.)

--

Check out the forum guidelines!

Topic locked