We are preparing a new hosting service and during the tests when trying to connect between WHMCS and Cloudmin we had the following error
CURL Error: 7 – couldn’t connect to host
Fun, I immediately check the connection between the machines where the WHMCS and the Cloudmin are, everything works. I'm checking the 10000th port and it's open and I have access to it 🙄 . Fun!
I'm doing a quick cloudmin server
tcpdump -i br0 host WHMCS_IP
and for mine (not very big) amazement I see that trying to connect to the 80's or 443 (if SSL is enabled) ports without asking me for one. By default, webmin and cloudmin, which is an application to the former, run on SSL 10000 port. Because this stupid system is IonCube encrypted, you can't edit your code to fix Indian nonsense, so you have to take a radical approach.. Before leaving the system, I replace the destination port with iptables
iptables -t nat -A OUTPUT -d cloudmin_ip -p tcp -m tcp --dport 443 -j DNAT --to-destination cloudmin_ip:10000
where you replace cloudmin_ip with the IP of your cloudmin installation. After this small manipulation, the connection between WHMCS and Cloudmin took place, but the module still has other problems besides this 😆
In general, for a year of using WHMCS I am extremely disappointed with it – it is quite wooden, support team support is slow, the documentation of the code and various other things diverge from reality, quite a lot of bugs and is quite wooden. If I knew it was so bad I would prefer to use it with a reset license instead of giving 300$ for something that works somehow!
http://www.youtube.com/watch?v = GF2-TKfQOsk