Control Web Panel

WebPanel => Addons => Topic started by: rikuslouw on April 04, 2020, 12:26:32 PM

Title: WHMCS not connecting to cwp
Post by: rikuslouw on April 04, 2020, 12:26:32 PM
Hi guys

I am still quite a noob to this, Ive bought a dedicated with cwp.Pro preinstalled the whole 9 wards. trying to link to my whmcs system. Under the servers it shows connected can log in to the panel etc.

When ordering a service it does not automaticly create the package on the server:

Tried following:
API with IP
API with %
Title: Re: WHMCS not connecting to cwp
Post by: ejsolutions on April 04, 2020, 12:35:32 PM
.. the whole 9 wards.
FYI: the phrase is "whole 9 yards" - unless it's to handle Covid-19  ;)
Title: Re: WHMCS not connecting to cwp
Post by: rikuslouw on April 04, 2020, 12:49:29 PM
 LOL....Suppose to be yes.

Oh also added ips to firewalls
Title: Re: WHMCS not connecting to cwp
Post by: CoriaWeb Hosting on April 04, 2020, 02:20:57 PM
You have to open this port in the firewall:

2304
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 21, 2020, 09:02:26 AM
The same thing happens to me, do not create the users, I have made the configuration of Add an IPV4 whitelist entry
Average udp 2301 to 2304
Open TCP \ UDP ports
2304 I don't know what else I can do, could someone advise me thanks
Title: Re: WHMCS not connecting to cwp
Post by: CoriaWeb Hosting on April 21, 2020, 09:13:03 AM
The same thing happens to me, do not create the users, I have made the configuration of Add an IPV4 whitelist entry
Average udp 2301 to 2304
Open TCP \ UDP ports
2304 I don't know what else I can do, could someone advise me thanks

It works for us simply by opening port 2304.

Try this command from the server where you have the WHMCS system and tell me if it gives you an error:

Code: [Select]
curl -k "https://IPCWP:2304/v1/account" -X POST --data "key = PgvuEjKHRDbL1BB5BJxe9r4c5MjDFRz6Ncax5Lu70Qzsl" --data "action = list"
Greetings!
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 21, 2020, 12:40:09 PM
He tells me this

csbJmS8Jr" --data "action = list"
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /:2304/v1/account was not found on this server.</p>
</body></html>
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 21, 2020, 12:45:40 PM
I have also tried two accounts that I have

thanks
Title: Re: WHMCS not connecting to cwp
Post by: josemnunez on April 21, 2020, 02:14:00 PM
You must replace the key port with your api key, I'm sure we will have another answer
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 22, 2020, 07:25:02 AM
in the comand I have put my api key
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 22, 2020, 07:26:13 AM
He tells me this

csbJmS8Jr" --data "action = list"
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /:2304/v1/account was not found on this server.</p>
</body></html>
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 22, 2020, 04:18:42 PM
I have disabled the firewall and it remains the same someone could help me thanks
Title: Re: WHMCS not connecting to cwp
Post by: josemnunez on April 22, 2020, 06:51:59 PM
Please remove the blanks in

  --data "action = list"

  --data "action = list"
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 23, 2020, 05:42:03 AM
Thanks
curl (7) failed connect (my ip server) 2304 connection refused
Title: Re: WHMCS not connecting to cwp
Post by: CoriaWeb Hosting on April 23, 2020, 09:28:36 AM
Thanks
curl (7) failed connect (my ip server) 2304 connection refused

That's because you haven't opened port 2304.

Greetings!
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 23, 2020, 11:14:22 AM
the port is open
TCP
IN: 20, 21, 22, 25, 53, 80, 110, 143, 443, 465, 587, 993, 995, 2030, 2031, 2082, 2083, 2086, 2087, 2095, 2096, 2304
OUT: 20, 21, 22, 25, 53, 80, 110, 113, 443, 2030, 2031, 2082, 2083, 2086, 2087, 2095, 2096, 587, 993, 995, 2080, 2443, 2304
UDP
IN: 20, 21, 53, 2304
OUT: 20, 21, 53, 113, 123, 2304

 Whitelist configuration
UDP   IN   ipv4 (Source)   2301 to 2304 (Destination)   CWP: allow a client to connect from ''ipv4'' via ''udp'' to port(s) 2301 to 2304

I also tried
TCP This server to connect to: TCPA specific port 2304
Title: Re: WHMCS not connecting to cwp
Post by: intechnologics on April 23, 2020, 06:31:24 PM
it doesn't work for me

User API port 2302 check: OK
Oauth query check: OK
User API folder check: OK
External API port 2304 check: OK
External API files and htaccess : OK
CSF Firewall status check: ENABLED
TCP_IN for port 2304 set in /etc/csf/csf.conf: OK
TCP_OUT for port 2304 set in /etc/csf/csf.conf: OK
Title: Re: WHMCS not connecting to cwp
Post by: icik9 on October 04, 2022, 07:26:45 PM
Hello, i have some vps, i make one for whmcs, another for cwp7 .

i have plesk in another vps :

 whmcs <> plesk = ok!
the command
Code: [Select]
curl -k "https://000.00.000.00:2304/v1/account" -X POST --data "key=u24y8dO30ZwI1CHfmZLK5M6cuh0UUx2f2A3RpCNx82E1ExLyMqPALsEvihrGbFUvCxHtwP" --data "action=list" works and give me th result attended .

I install php-fpm, cgi, ioncube, install the BDD, whmcs is ok.

I type
Code: [Select]
curl -k "https://000.00.000.0:2304/v1/account" -X POST --data "key=u24y8dO30ZwI1CHfmZLK5M6cuh0UUx2f2A3RpCNx82E1ExLyMqPALsEvihrGbFUvCxHtwP" --data "action=list" another time after installs, in ssh and... TADAMMM
Code: [Select]
curl: (28) Failed to connect to 000.00.000.0 port 2304: Connection timed out
.... i really, but really dont understant, and when i curl -k in another of my vps, it works.... help :p
Title: Re: WHMCS not connecting to cwp
Post by: josemnunez on October 04, 2022, 11:35:21 PM


Connection timed out ->

You are doing something wrong!

1- Check the Apikey and that you have permission to see the return list

2. That the port is open, from whmcs to cwp and vice versa

3. I will use the % option in the apikey instead of the ip