Errors at the end of install, unable to connect to 8080

Discussion in 'Installation/Configuration' started by schwim, Dec 21, 2018.

  1. schwim

    schwim Member

    Hi there everyone!
    Troubleshooting script results: https://hastebin.com/puzosatodi.md
    Fresh Deb 9 install, updated
    ISPC version installed via:
    Code:
    cd /tmp; wget --no-check-certificate -O installer.tgz "https://github.com/servisys/ispconfig_setup/tarball/master"; tar zxvf installer.tgz; cd *ispconfig*; bash install.sh
    
    I am unable to connect via IP:8080:

    At the end of my ISPC install process, this showed:
    Then when trying to remove spamd, as instructed in the how-to, again:


    I'm not sure where to go from here. I would be happy to provide more information if needed. Any help would be greatly appreciated.

    Thanks for your time!
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The server hostname was not set correctly before you started the install and that's why amavis fails.

    What's the output of the commands:

    hostname

    and

    hostname -f
     
  3. schwim

    schwim Member

     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    As you see from result of the second command, the FQDN hostname is not set correctly. Check /etc/hosts file.
     
  5. schwim

    schwim Member

    It's missing the important bits:
    I'm not sure how to determine what that second line should look like on this server.
     
    Last edited: Dec 21, 2018
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Code:
    IP server2.schwimserver.com server2
    replace IP with your public IP address.
     
  7. schwim

    schwim Member

    Ok, I found the ipv6 entry in Linode's control panel. I edited /etc/hosts and rebooted:
    On reboot, 45.79.22.XXX:8080 or server2.XXX.com:8080 still results in a refused connection. Leaving off the port results in a successful connection and default Apache page. Am I still failing to do something to fix what for some reason didn't happen on install?
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    The problems with auto installers is that you don't see when something fails behind the scenes and this can happen easily when the base system does not match exactly the requirements of the installer, that's why I personally prefer the normal setup (aka. perfect server guides). But ok, you've chosen the auto installer now, so let's try to find out what has failed:

    Run the test script and post the results:

    https://www.howtoforge.com/community/threads/please-read-before-posting.58408/
     
  9. schwim

    schwim Member

    I only used the script because that's the process that was the top result on searching install of ISPConfig. I'd be just as happy to follow another tutorial. When you say perfect server guide, do you mean this one? I note it's not available for debian, is the preferred OS for ISPC Ubu? If so, I'll wipe the node and install it in Debian's place.
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    The perfect server guides are available for all OS that ISPConfig supports. See ISPConfig documentation page:

    https://www.ispconfig.org/documentation/

    And a search 'perfect server debian' gives the right guide (in apache and nginx flavour) as top 1 and 2 result in google and howtoforge search.
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    But as mentioned in my post above, run the test script, post the result, and we can see how to fix your current install without reinstlling everything.
     
  12. schwim

    schwim Member

    IT'S TOO LATE!
    :D
    I wanted to see what all the install process entailed so I just slapped a new image on the node and followed the perfect server tutorial. It was incredibly easy to follow and so well done, there wasn't a single hiccup during the process.

    Thank you so much for the fantastic tutorial!
     
    till likes this.

Share This Page