Skip to main content

Failed to connect to port 2083 Connection refused

Manish Laungani
We have set up a WordPress multisite, using WP-ultimo. and while heading towards the domain mapping part, we were asked to add a snippet of code to the WP-config.php file ( code displayed below). When we try to add the domain as an alias to the account site, WP throws an error "Failed to connect to mydomain.com port 2083: Connection refused". Typically the code is supposed to connect to the cpanel so that an alias can be created further to which SSL will be installed to that site. We have spoken to the guys who developed the plugin, and it seems they have nothing to do with it. Does anyone have any idea what could be the issue here ?

Comments

15 comments

Date Votes
  • cPanelMichael
    WP throws an error "Failed to connect to mydomain.com port 2083: Connection refused".

    Hello @Manish Laungani, I'm not sure how the WordPress plugin is designed, however as a first step I recommend contacting your web hosting provider to have them verify that no firewall rules on the server are configured to restrict traffic over port 2083. Thank you.
    0
  • Manish Laungani
    Hi @cPanelMichael, thanks for your prompt response. We wrote to out hosting guys, and this was their response. Dear client, "By default, we do not block ports on the servers except for the NTP. We can see that 2083 is not open on the server, so you should configure it from within your system. Unfortunately, we do not have access to your OS, so we suggest you should check the settings. Thank you.
    Yours sincerely,
    Hostkey Support Team
    " So, here is what I'm curious about... 1) If the 2083 port isn't configured, then how are we able to access cPanel with these 2 links - mydomain.com/cpanel and mydomain.com:2083. Also, I should have mentioned both these links don't work with http, only https 2) How do I resolve this? Regards Manish
    0
  • cPanelMichael
    Hello Manish, It's difficult to know the exact reason for the failure without more information about the script you are using. Can you share an example of the lines of code that are used with this custom script? Ensure to paste the example in CODE tags and replace any identifying information about your server or login details with example data. Thank you.
    0
  • Manish Laungani
    So, I did a little google of my own and came across this thread (). I followed those suggestions, got the firewall configuration done. But, the issue still seems to be the same.
    0
  • Manish Laungani
    Here is the code added to the wp-config.php file [PHP]/* WP Ultimo: Adding automatically domain syncing to cPanel */ define('WU_CPANEL', true); define('WU_CPANEL_USERNAME', 'dbuser'); define('WU_CPANEL_PASSWORD', 'dbpassword'); define('WU_CPANEL_HOST', 'mydomain.com'); define('WU_CPANEL_PORT', 2083); /* end WP Ultimo */[/PHP]
    Hello Manish, It's difficult to know the exact reason for the failure without more information about the script you are using. Can you share an example of the lines of code that are used with this custom script? Ensure to paste the example in CODE tags and replace any identifying information about your server or login details with example data. Thank you.

    i
    0
  • cPanelMichael
    Hello @Manish Laungani, You'll need to report this issue to the developer of the WordPress plugin you are using so they can investigate and verify why the plugin is not working on the cPanel & WHM server your shared account is hosted on. Let us know the outcome once you hear back from them. Thank you.
    0
  • Manish Laungani
    @cPanelMichael, please refer to the first post in this thread. What you have suggested is exactly what was my first step in trying to resolve the issue. The dev pointed out that the plugins trying to access the cPanel using this URL example.com:2083, but that does not resolve. But, https//:example.com:2083 which resolves fine. Also, I was informed that 2083 is SSL port for cPanel and 2082 is a non-SSL port for cPanel, which makes it weirder. Here's a direct question, how is
    0
  • cPanelMichael
    Here's a direct question, how is WHM >> Host Access Control to make sure port 2083 (cpsrvd) isn't blocked or restricted there. Thank you.
    0
  • Manish Laungani
    HI @cPanelMichael, we have the root access to the server ( it's not shared hosting). Here is the screenshot of the host access control page from our WHM. - Removed -
    0
  • cPanelMichael
    Hello @Manish Laungani, Can you add the image directly to the post as an attachment using the "Upload A File" button at the bottom of the post response field? Thank you.
    0
  • Manish Laungani
    Hello @cPanelMichael, here's the screenshot. Regards Manish
    0
  • keat63
    If you can get to '
    0
  • Manish Laungani
    If you can get to '

    Yes, that what I thought at first, but it actually breaks the code. I also checked with the devs of the plugin, they very specifically recommend against it.
    0
  • Manish Laungani
    I'm in constant touch with the dev, and they say that the "It looks like your server firewall is, in fact, blocking outgoing calls to port 2083, which results on the Connection refused messaged... you need to open port 2083 for outgoing access on iptables." Does anybody know how to do that? I checked the IP tables by using the below command, and it seems that the 2083 port isn't blocked...but, I'm not sure if I'm reading it right. Could anyone check the same for me? sudo iptables -S
    0
  • cPanelMichael
    Hello @Manish Laungani, I recommend installing a firewall management utility such as CSF to make managing your custom firewall rules easier: How to Configure Your Firewall for cPanel Services - cPanel Knowledge Base - cPanel Documentation Let me know if this helps. Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post