the latest SolidCP WHMCS module is updated in the WHMCS marketplace (but the changelog is still not updated there).
v. 1.1.2 – 05 Dec. 2016
– Compatible with WHMCS v7 and PHP 7 (WHMCS < 6 and PHP < 5.3.7 are NOT supported anymore)
– Transition to new DB framework in WHMCS due to deprecated old database connections
– Fixed adding addons in Admin panel
– German module language added in admin area
– Small bug fixes
Feel free to download on https://marketplace.whmcs.com/product/1430 and don’t forget to leave a 5 star vote :).
Yes, the hostname is the same as the URL I used to access it via a browser (with the port added), and also the IP which I also confirmed via browser access with the port added.
There is no SSL cert so I have not clicked that option.
I also tried changing the hostname to the IP address to see if that helped (that is how my other linux server is configured, but it is the local machine that the WHMCS installation is on, whereas the SolidCP is obviously remote).
Thanks for your reply Marco.
So I realised that I hadn’t actually tried connecting from the Linux server directly and gave it a go. Here was the outcome:
[root@vps ~]# wget -p http://siteURL.com:9002
–2017-11-29 09:50:44– http://siteURL.com:9002/
Resolving siteURL.com… ###.16.###.234, ###.230.###.128
Connecting to siteURL.com|###.16.###.234|:9002… failed: Connection refused.
Connecting to siteURL.com|###.230.###.128|:9002… failed: Connection refused.
(actual URL & IP substitutued for “siteURL.com” & ###)
So the connection is being refused even though I have the site bindings set to allow access on the port:
SOAP is installed and it is what is throwing the error message when it can’t connect. What is blocking it on the Windows Server to make it get refused?
maybe a firewall issue? Are the WHMCS server and the SolidCP Enterprise Server in the same internal network? If yes, it could also be an issue with a loop, if you try to connect with the external FQDN? Maybe you can try to connect with the internal IP? This would be also my recommendation not to expose port 9002 unsecured to the internet.
You can try to enable the ICMP connection in the Windows firewall and try to ping the Win server from the Linux server. If this is successful, then it should be an issue with the IIS configuration/firewall. If it’s also unsuccessful, then it’s a network issue.
- Views10543 times
- Answers26 answers