chrigu Posted July 13, 2018 Share Posted July 13, 2018 Dear Community. I have the Problem, that the connection to my plesk is not working. I get the error: FAILED: Error code: 0. Error message: Curl error: [7] Failed to connect to myurl.net port 8443: Connection refused. Does anyone of you have a solution for me? Thanks a lot! 0 Quote Link to comment Share on other sites More sharing options...
redit Posted July 13, 2018 Share Posted July 13, 2018 Sounds like a firewall or ACL rule. Might be worth just checking these two options on the Plesk server that you are trying to connect to. Also see if you could either wget or telnet to your Plesk server from the command line of your WHMCS box. wget https://myurl.net:8443 or telnet https://myurl.net:8443 0 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 13, 2018 Author Share Posted July 13, 2018 10 minutes ago, redit said: Sounds like a firewall or ACL rule. Might be worth just checking these two options on the Plesk server that you are trying to connect to. Also see if you could either wget or telnet to your Plesk server from the command line of your WHMCS box. wget https://myurl.net:8443 or telnet https://myurl.net:8443 Thank you for your help. I tried via SSH from my Server, where WHMCS is installed. I got Permisson Denied, I think that mean, Plesk blocks the requrest? Can you tell me, where to allow that? 0 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 13, 2018 Author Share Posted July 13, 2018 I have also tried to accept the IP via SSH, and restartet server. Same result.https://support.plesk.com/hc/en-us/articles/115001078014-How-to-manage-ports-and-firewall-rules-on-Plesk-for-Linux-server 0 Quote Link to comment Share on other sites More sharing options...
wp4all Posted July 16, 2018 Share Posted July 16, 2018 Hi chrigu, please proof if you allow incoming traffic all other incoming traffic in your FW settings: If you block specific ports you need to create a new role and allow port 8443 if still standard. Greetings and best regards Christian 1 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 16, 2018 Author Share Posted July 16, 2018 Hi Christian. Thanks for your idea's. I have the rule active and also added the rule you told me. Its the same issue 0 Quote Link to comment Share on other sites More sharing options...
wp4all Posted July 17, 2018 Share Posted July 17, 2018 Hi, du hast ein Curl Fehler das ist ein ganz anderer Ansatz. Gruß Christian 0 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 17, 2018 Author Share Posted July 17, 2018 Sorry, this information doesnt helps. curl is activated on both servers 0 Quote Link to comment Share on other sites More sharing options...
wp4all Posted July 17, 2018 Share Posted July 17, 2018 (edited) HI Chrigu, could be possible that Curl is installed but maybe the wrong version --> you have errors You should check your version and maybe this post helps also : https://support.plesk.com/hc/en-us/articles/214029229-How-to-update-cURL-to-the-latest-version-on-a-Plesk-server check your version with curl -V curl 7.61.0 (x86_64-redhat-linux-gnu) libcurl/7.61.0 NSS/3.36 zlib/1.2.7 libpsl/0.7.0 (+libicu/50.1.2) libssh2/1.8.0 nghttp2/1.31.1 Release-Date: 2018-07-11 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz HTTP2 UnixSockets HTTPS-proxy PSL Metalink Newest Version is 7.61 With more information it would be easier to analyse (logs) Greetings Christian Edited July 17, 2018 by wp4all 0 Quote Link to comment Share on other sites More sharing options...
wp4all Posted July 17, 2018 Share Posted July 17, 2018 (edited) Jep, here it is : [root@vps01 ~]# curl --verbose https://h2793268.xxxyyyzzz.net:8443 * Rebuilt URL to: https://h2793268.xxxyyyzzz.net:8443/ * Trying 81.xxx.yyy.zzz... * TCP_NODELAY set * Connected to h2793268.xxxyyyzzz.net (81.xxx.yyy.zzz) port 8443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: none CApath: none * loaded libnssckbi.so * Server certificate: * subject: E=info@plesk.com,CN=Plesk,O=Plesk,L=Schaffhausen,C=CH * start date: Jul 11 11:41:34 2018 GMT * expire date: Jul 11 11:41:34 2019 GMT * common name: Plesk * issuer: E=info@plesk.com,CN=Plesk,O=Plesk,L=Schaffhausen,C=CH * NSS error -8172 (SEC_ERROR_UNTRUSTED_ISSUER) * Peer's certificate issuer has been marked as not trusted by the user. * stopped the pause stream! * Closing connection 0 curl: (60) Peer's certificate issuer has been marked as not trusted by the user. More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. you have got a cert problem, if you fix it you will get access to your Panel. Curl is not able to accomplish a connection 😁 Greetings Christian Edited July 17, 2018 by wp4all 0 Quote Link to comment Share on other sites More sharing options...
wp4all Posted July 17, 2018 Share Posted July 17, 2018 (edited) Additional Info to my post above: Try it maybe with your Domain or IP but not with the Server Hostname from your Provider : Insted of https://h2793268.xxxyyyzzz.net:8443 you should try to get access with the IP or Domain pointing to the IP under which you have installed Plesk then maybe you will have an valid SSL cert. Plesk creates after the installation process an self generated cert you should see an message like --> This server is powered by Plesk. Log in by browsing https://111.111.111.111:8443/ or https://vps01.xxxx.yyyy.zzzz:8443/ You can log in as user 'root' or 'admin'. To log in as 'admin', use the 'plesk login' command. Use the 'plesk' command to manage the server. Run 'plesk help' for more info. connecting via ssh on your Server. Greetings Christian Edited July 17, 2018 by wp4all 0 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 18, 2018 Author Share Posted July 18, 2018 Thanks for your ideas. 1. I showed the curl version, its 7.47.0, see screenshot below 2. I called my hoster from the root server. There is no way, to get a cert for this hostname, because its a url from them 3. I tried an url, which is active on the server, but I get the same error. 4. I tried wget with a live URL, and I get error's, thats for your advice there! I get the certificate error, see screenshoe below. I use lets encrypt to create the cert. Do you have an idea, how I can fix that? Thanks a lot! 0 Quote Link to comment Share on other sites More sharing options...
chrigu Posted July 18, 2018 Author Share Posted July 18, 2018 I found the Problem! The problem was the webserver, FROM where I asked the request. I tried another server and it worked. I white listet the server and it works great... 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.