Trying Cloudmin for the first time, I had installed it on a fresh CentOS 6.3 system by running ‘cloudmin-kvm-redhat-install.sh’. However, unfortunately, it was not available on https://host.mydomain.com:10000 As I understood Cloudmin installation script didn’t install Apache, so no wonder webinterface was not available.
Then I proceeded to install Virtualmin by running its ‘install.sh’ script and only then I could login to https://host.mydomain.com:10000 Now I have all three: Virtualmin, Cloudmin, Webmin, which is fine by me and I know they can run together.
However my question is what is minimum requirements to get Cloudmin installed? I will not be creating virtual servers on the main server, so I don’t really need Virtualmin, I only need Cloudmin on it. Is it at all possible to have only Cloudmin? Should’ve I had Apache preinstalled for this?
The Cloudmin installer should have installed Webmin alongside with it. It does not need Apache; since it’s a Webmin module, it uses Webmin’s built-in mini webserver.
You might want to repeat the process and make sure that Webmin gets installed by the Cloudmin script, or check out what went wrong (by checking the install log e.g.) if it doesn’t.
Unfortunately, the server is remotely located and it is a bit problematic for me to re-install it and since after installing Virtualmin everything works I am fine for now. However I just wanted to turn your attention to the fact that Cloudmin doesn’t install on a fresh CentOS 6.3. For some reason Webmin’s built-in mini webbrowser did not work in my case.
I went to my data-center, re-installed the whole system with cloudmin and again experienced the same problem. After some digging found out fresh CentOS blocks port 10000. After opening the port I was finally able to see the Cloudmin interface.
Now when I am with freshly installed Cloudmin without Virtualmin, I am hitting another problem.
I decided to devote a new domain name to Cloudmin server, so that all the VPSs would have automatically created DNS-records like: vps1.mydomain.com, anyshorthost.mydomain.com, etc.mydomain.com. In order to achieve this I have registered two private nameservers: ns1.mydomain.com and ns2.mydomain.com and updated the nameservers for the domain on my GoDaddy control panel.
This method would work on a Virtualmin server allowing to manage all the DNS records on the server itself, I just needed to add respective NS and A records for the two nameservers through Virtualmin’s DNS editor for the domain name.
Now when I don’t have Virtualmin, I went to Webmin - Servers - BIND DNS Server and clicked “Create master zone.” and created a zone for my domain name mydomain.com, which contains:
$ttl 38400
@ IN SOA ns1.mydomain.com. info.mydomain.com. (
1355344362
10800
3600
604800
38400 )
@ IN NS ns1.mydomain.com.
@ IN NS ns2.mydomain.com.
www IN A xx.xx.xx.xxx
ns1 IN A xx.xx.xx.xxx
ns2 IN A xx.xx.xx.xxx
Mismatched NS records, Nameservers did not respond, Missing nameservers reported by your nameservers, Missing SOA record, Missing MX Records, Missing WWW A Record.
This kind of things were so easy to troubleshoot with Virtualmin, but I really do not need it on this server and don’t want to install it only to get a single problem resolved. Is there any clear guidance on how to set DNS for a cloudmin server? I’ve read through http://www.virtualmin.com/documentation/cloudmin/vm/register, it doesn’t help much since it works only if I use external namesevers and point my domain to the server through A-record and I want my server to take full care of DNS-records internally.
It is a bit hard to debug this nameserver issue without knowing the actual domain names and IP addresses involved. Could you post those? Anything else would be more or less guesswork.
Yep, you can email the details to locutus “AT” tianet “DOT” de. Please excuse the obfuscation, this is a public forum, and spammer crawlers are everywhere.
(@Eric/Joe: This forum badly needs a PM function!)
Okay, the entries at the registrar look okay, nameserver entries work, glue is present. The IP of your server can be pinged and traced.
BIND on your server does not respond though. Since I’m getting a timeout, and not a REJECT, it is most likely that a router or firewall is blocking the packets.
You might want to check if BIND is running on your server and listening on port 53 on all IPs: netstat -upln | grep 53 should turn up results.
Check if a local firewall is blocking port 53: iptables -L -n
Otherwise check with your hoster if ports need to be opened.
Thanks for your time. Nothing is blocking the port 53. I made sure it is open in firewall. I’ve just sent you an e-mail with access info, could you please take a look?
I logged in to your Cloudmin, and checked the system named “ns1.yourdomain.tld”. It looks like the eth0 interface does not have an IP address, and thus BIND is listening only on localhost.
You’d need to tell us/me more about your intended networking setup of the host and your virtual machines.
Unfortunately, my experience with Cloudmin is very limited (i.e. near zero ), so I can’t really say how you assign IP addresses, configure routing or port forwarding and stuff. Eric would need to take over here if you can’t figure it out yourself.
Oh, never mind that. I executed the ifconfig in a “root shell” window, and the “br0” interface scrolled out of view. It seems like your external IP is assigned to a network interface named “br0” (a bridge?). As I said, my experience with KVM is about zero (I use VMware ESXi myself)… So I can’t give much advice here.
You need to configure BIND to listen on all IP addresses, right now it’s listening only on 127.0.0.1.
Thank you very much for showing me right direction.
What is frustrating is that this was fresh Cloudmin install on a fresh CentOS 6.3 install. I did not make any changes, just following the Cloudmin manuals on this site and it was Cloudmin installation that replaced eth0 with br0. As I understood it needed to do so to make all guest VPSs to share network connection.
But now how can I make DNS records of my main domain to resolve?
