ISPCONFIG 3 apache vhost not working

Discussion in 'ISPConfig 3 Priority Support' started by Bentino, Mar 8, 2020.

  1. Bentino

    Bentino New Member HowtoForge Supporter

    Hello,
    I have ISPconfig3 everything work fine all service running but few days ago I cannot access all site on my server
    I have done these steps below.
    • I use Digitalocean’s DNS (the vanity DNS), all domains pointed to my server.
    • All services is running, no abnormal log.
    • Firewall is enable (port 80/443 is allowed)
    • ISPconfig on port 8080 and all applications on 8081 is work fine.
    • All Let's encrypt certificates are renewed.
    Only vhost files has problem I cannot access all sites on this server.
    How can I fix this?
    I also attache my sample vhost file
    Thank you.
     

    Attached Files:

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The vhost looks fine. Which exact error message do you get in the web browser when you try to access the site?
     
  3. Bentino

    Bentino New Member HowtoForge Supporter

    Just timeout, I have no idea why it happen because it work until few days ago.
     
  4. Bentino

    Bentino New Member HowtoForge Supporter

    However you can try on this IP
    188.166.196.215
    When you try to connect this IP you will see request timeout, if it working you should see default apache page.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

  6. Bentino

    Bentino New Member HowtoForge Supporter

    Attached Files:

  7. till

    till Super Moderator Staff Member ISPConfig Developer

    For a test, try to disable the ufw firewall:

    sudo ufw disable

    and then test if you can access the web server now. You can re-enable it afterwards with:

    sudo ufw enable
     
  8. Bentino

    Bentino New Member HowtoForge Supporter

    It does not work, site still no response.
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Is the server behind a router? is the IP 188.166.196.215 the only IP of the system or does it also has an 'internal' IP?
     
  10. Bentino

    Bentino New Member HowtoForge Supporter

    188.166.196.215 just floating IP the real IP is 68.183.186.173
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    Does it work on the other IP, at least to reach the apache server?

    And then try this on the shell of your server:

    cd /tmp
    wget http://188.166.196.215
    wget http://68.183.186.173

    does it time out as well or is wget able to download the apache default page?
     
  12. Bentino

    Bentino New Member HowtoForge Supporter

    both IPs wget can load a HTML page from server but when I put this IPs on web browser it doesn't work
    I also add output from wget in file attachment.
    Thank you
     

    Attached Files:

  13. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, this is a clear indication that the http and https ports are blocked in an external firewall. The datacenter where you host that server has probably such a firewall, check the controlpanel of the server / vserver that the server hosting provider probably offers you and if you don't find anything, contact the support and tell them that apache is reachable locally on the server, local firewall is off but you can't connect to apache from the internet so that they can check their firewall system.
     
    Bentino likes this.
  14. Bentino

    Bentino New Member HowtoForge Supporter

    Thank you.
     
  15. Bentino

    Bentino New Member HowtoForge Supporter

    Digitalocean said no firewall attach on my droplet, how can I go?
    Thank you.
     

    Attached Files:

  16. till

    till Super Moderator Staff Member ISPConfig Developer

    Do you have any idea what you did on the server at the time the issue started? And di you contact the support and asked them, it might be that they applied a firewall or protection or whatever nonetheless, so it's important that you contact the support, tell them what I told you and let them test the connection on port 80 and 443.
     

Share This Page