Won't accept incoming connections

Discussion in 'Server Operation' started by Manlove, Dec 10, 2015.

  1. Manlove

    Manlove Member

    Hi. I have a recently installed ispconfig setup on a VS, with the latest stable version, on Debian Jessie. It was working fine, I added a few accounts, changed the webmail setup from Squirrelmail to Roundcube and finally added the default ispconfig firewall rule. Everything working perfectly.

    I left it for a week, came back to add a new email account, but can't login. Trying the IPADDRESS:8080, IPADDRESS/webmail just returns a connection error. I can login to the server withpout any problem, so the first thing I did was to change the iptables to accept all, but that hasn't helped. If I restart the apache service it reloads the configured firewall.
    Code:
    The remote device or resource won't accept the connection
    Detected
    Detected 
    The device or resource (***.***.**.**) is not set up to accept connections on port "8080".
    The device or resource (***.***.**.*8*) is not set up to accept connections on port "The World Wide Web service (HTTP)".
    What might be causing this?
     
  2. sjau

    sjau Local Meanie Moderator

  3. Manlove

    Manlove Member

    Yes I did, so you might be on the right lines. The last thing I did was to renew the certificate and run an ispconfig update but logged off with it all working. I can ping in and out, I've tried both http and https connections and I tried other browsers. I get no certificate warnings, just zero connection.
     
  4. Manlove

    Manlove Member

    Would running another update help?
     
  5. sjau

    sjau Local Meanie Moderator

    You could reconfigure the services.. That will also ask you to generate new certs etc or using https. Not sure where else that is stored:

    Code:
    cd /tmp
    wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz
    tar xvfz ISPConfig-3-stable.tar.gz
    cd ispconfig3_install/install
    php -q update.php
    
     
  6. Manlove

    Manlove Member

    That seems to be the answer. I reinstalled the package and reconfigured the certificate (using the same info) and it's all working now. Thanks
     

Share This Page