I have just built 4 domains/virtual server for personal use and so far so good.
But I am unable to access each Administration URL using the FQDN… https://www.mydomain.co.uk: 10000 (This is not working).
However, I can use the overall virtualmin using my local IP: 192.168.0.100: 10000 and then on the left-hand side I can use the required domain from the drop-down list.
I am sure there must be a way to access the admin panel for a specific website using FQDN or at least the Public IP: 10000 This will help me manage my website from anywhere - especially when I am not at home.
DNS isn’t working. You probably haven’t setup a glue record at your registrar, but could be any number of other things.
You should separately confirm whether it is accessible on the public IP. If it isn’t, then obviously the FQDN will never work. Some SOHO routers don’t allow routing from inside to the public IP, so it won’t work from inside the network. Others just require addition of port forwarding rules.
I am not using SOHO routers… I am using a business router provided to me by my ISP. I have also enabled port forwarding on the router from my public to 192.168.0.100
I have not set up a glue record as I had no clue what it is, but now that I have done some research and even tried to set it up, this looks complicated and dangerous to me.
So I have one Ubuntu server and 4 domains with 1 domain having 3 subdomains (making it 7 virtual machines) and all of them have their own Administration URL… so if I want to access all those 7 websites from their URL:1000, am I suppose to make 7 entries in GoDaddy’s admin panel?
Is that not dangerous? It’s not like I am moving from GoDaddy to CDN, if you know what I mean.
Both this URLs are accessible via: https://192.168.0.100:10000 and all virtual servers are listed on the left hand side, I need to pick one of them and do the required configuration.
But if I can access the FQDN, I believe I will get only one system details to edit it. However, the no. of VM on LHS is not important here - what is important is to get it working and then I can decide which is better option for me.
So I am assuming, everything is working as expected: DNS, SSL, port forwarding etc.
Hope this extra information helps. Any suggestion will be highly appreciated.
That’s exactly the kind of router I’m talking about. SOHO means “Small Office/Home Office” and refers to a huge variety of router by many manufacturers. Your router may not be able to route back to the LAN via it’s public IP, or it may need some additional configuration to do so. That’s not something I’m going to be able to help you with, I’m not an expert on routers of that sort (or any sort, really, as it’s been more than a decade since I was responsible for network administration). This isn’t really a Virtualmin problem. It’s a problem with your router.
Note that you might still be able to do what you want (manage the server from outside your network). The problem I’ve described is that local devices cannot reach other local devices that have port forwarding setup on the public IP. But, remote devices (out on the internet) can. Assuming, of course, port forwarding is setup correctly.
The post you mentioned seems to have some wrong ideas about SSL/TLS certificates (they are not tied to ports), so maybe ignore that bit.
If you’re using GoDaddy for your DNS hosting, you don’t need glue records, but you do need A records for any names you want to point to your public IP.
I already have the A record set and probably that’s why I am able to access all my domains and subdomains from the internet (from anywhere).
Based on your suggestion that “Your router may not be able to route back to the LAN via its public IP”? I did some online research and few people suggested this can be achieved by implementing "Hairpin NAT " and/or “split-horizon DNS”, went thru those details as well, but I am worried that I will end up creating more problem for myself rather than fixing it.
All I want to achieve is: when I am let’s say at my friend’s place and I need to check/update something on my server, I should be able to access it using FQDN
(Administration URL: https://www.domain1.com:10000/) because from there I won’t be able to access it using: https://192.168.0.100:10000)
Just to let you know my ISP does not support IPV6.
Just test it with your phone or some other device not on your local wifi. If it’s the router problem, you’ll just need to access it locally on the local IP or setup views in DNS (that’s the “split-horizon” thing). But, it’s a lot of trouble for not a lot of benefit. You could just have a different hostname you use internally (public DNS can host a private IP, it doesn’t care…I do it all the time for VPN connections and the like).
Again, I don’t know how to fix your router. Not my area. But, if it’s what I think it is, you don’t need to do anything complicated or scary to work around it (assuming you have port forwarding setup correctly).
Just tried on another laptop, making my mobile as a hotspot, still it did nto resolve - unable to launch: https://www.domain1.co.uk:10000
As far as port forwarding setup is concerned, I have port forwarded on my router for 192.168.0.x where x is the port of the server where virtualmin is running and all virtual servers are hosted. And all website sare accessible from outside… which I believe means it has been configured properly.
When you sayd, “Public DNS can host a private IP, it doesn’t care”, any pointer on how I can do that?
I agree with you and so I also want to fix one thing at a time… and my ONLY requiremnent is to be able to access teh admin pannel on: https:///www.domain.co.uk:10000 (even if I can access it on my local network, that will be my 1st achievement).
Where do you want me to update the A record? On Go Daddy DNS management pannel or somwhere in Webmin? If Webmin, can you pls let me know the path.
FQDN is one problem: When you do a name lookup for your domain, does it resolve the public IP of your router?
Accessing services running on your Virtualmin server from outside is the other problem: When you send a request to the public IP of your router, does it make it into the Virtualmin server, and does it make it back out? If not, that’s entirely a problem in your router. We can’t solve it, and have no idea how to solve it. It may be impossible to route to the public IP from inside the private network (this is a common limitation of low end routers).
Test them separately. When you try to browse to https://<your-public-ip>:10000 from outside your local network do you reach Virtualmin? If not, you have not solved that second problem, and you can’t expect https://<FQDN>:10000 to work. It’s not one achievement, it is two. Have you achieved “reaching the Virtualmin server on the public IP”? If not, you’re still needing to figure out how your router works and it’s outside of our area. We don’t know how to do it.
Is GoDaddy the authoritative name server for your DNS zone? Then you need to add it in GoDaddy’s UI. If your Virtualmin server is authoritative for your zone (i.e. you setup glue records for it), then you’d add it in Webmin.
You could also just add it to your hosts file, if you only have the one computer that you’ll be using to access it.
