First, let me say that I tried posting a very detailed post under this subject. When I clicked on submit it said the topic was created, but I can’t find the post. (Yes, I was logged in and I checked the Private box.) I’ve had a similar problem with other posts which I gave up on. I suspect something “forbidden” was in the posts, so I’m trying with only inocuous text.
I setup a virtual server in Virtualmin but I can’t see the site on the internet. How can I provide details to resolve this problem?
When creating the virtual server I selected “Setup SSLwebsite too” in enabled features and in IP address and forwarding ->Network interface I selected Virtual with IP, added the server ip addres and checked the “Already active” box.
A check of the domain at intodns.com (https://intodns.com/pennypenguingames.com) seems to be ok except something about MX records (see below) which I don’t understand but I don’t see how it could be relevant to this problem.
What do I need to do to get this site on the internet?
Your MX records that were reported by your nameservers are:
OK, I’ll try to give some details in a “spam friendly” manner.
I set up a domain as a top-level virtual server.
When creating the virtual server I selected “Setup SSLwebsite too” in enabled features and in IP address and forwarding ->Network interface I selected Virtual with IP, added the server ip addres and checked the “Already active” box.
All of the DNS records were created by the system. I haven’t added, deleted or altered any of the records.
When I try to see the site on the internet, I get the error page that Firefox can’t connect to the server amd Chromium gives a similar result.
What do I need to do to get this site on the internet?
Looks like you don’t have glue records pointing to your server. That’s handled at your registrar. Your records are being served by your registrar, which is not under control of Virtualmin and can’t be controlled by Virtualmin.
Also, please don’t use private forum posts (it turns out I can’t disable them without potentially revealing information that someone really intended to be private).
This topic is resolved.
Turns out this was a problem of slow propagation. I’m in Brazil and it appears it took quite a bit of time for the nameserver info to propagate to down here.