No ISPConfig Page Shown.

Discussion in 'Installation/Configuration' started by JDConnors, Feb 9, 2014.

Page 1 of 2
  1. JDConnors

    JDConnors New Member

    JDConnors, Feb 9, 2014
    #1
  2. JDConnors

    JDConnors New Member

    I've found that it doesn't matter if you enable ssl or not, it still comes up the same way.

    Must be a symlink of some sort?
     
    JDConnors, Feb 9, 2014
    #2
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you follow the guide to the letter, or dd you leave out some instructions?

    ISPConfig uses its own vhost, this vhost file is in /etc/httpd/conf/sites-enabled/. Maybe the include in your httpd.conf for the directory /etc/httpd/conf/sites-enabled/ is missing.
     
    till, Feb 9, 2014
    #3
  4. JDConnors

    JDConnors New Member

    Till,

    Followed to the letter. I didn't change anything.
     
    JDConnors, Feb 9, 2014
    #4
  5. JDConnors

    JDConnors New Member

    Till,

    NameVirtualHost *:80
    NameVirtualHost *:443
    Include /etc/httpd/conf/sites-enabled/


    It's there :confused:
     
    JDConnors, Feb 9, 2014
    #5
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, and in /etc/httpd/conf/sites-enabled/, you have a 000-ispconfig.conf and 000-ispconfig.vhost ?
     
    till, Feb 9, 2014
    #6
  7. JDConnors

    JDConnors New Member

    Yes, they are both located there.
     
    JDConnors, Feb 9, 2014
    #7
  8. JDConnors

    JDConnors New Member

    Guess it's stuck at that :)
     
    JDConnors, Feb 9, 2014
    #8
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Are you sure that you really access the correct server? Maybe the domain points to a wrong IP or the port is forwarded in a router to a different server or the router uses port 8080 itself.
     
    till, Feb 10, 2014
    #9
  10. JDConnors

    JDConnors New Member

    No router, no firewall on the box right now.

    It's located in DC and there is nothing being blocked.

    Squirrelmail works, awstats work.
     
    JDConnors, Feb 10, 2014
    #10
  11. sthevan79

    sthevan79 New Member

    any solution ?
    i also getting Apache test page only

    Thanks
     
    sthevan79, Mar 3, 2014
    #11
  12. JDConnors

    JDConnors New Member

    @sthevan79

    All I did was go thru the install again. I had a found a couple things I had missed and it works now.

    Probably the safest best is just verify you didn't miss a step along the way.
     
    JDConnors, Mar 3, 2014
    #12
  13. sthevan79

    sthevan79 New Member

    when installation does have any error
     
    sthevan79, Mar 3, 2014
    #13
  14. JDConnors

    JDConnors New Member

    Mine didn't have any errors either, but I missed putting line in.
     
    JDConnors, Mar 3, 2014
    #14
  15. sthevan79

    sthevan79 New Member

    r u using centos 6 os?
     
    sthevan79, Mar 3, 2014
    #15
  16. JDConnors

    JDConnors New Member

    Here is my 'fix' in another thread.


    If you are using CentOS, ensure that you have no 3rd party repo's enabled. ISPConfig needs be installed on a vanilla OS install.

    So, check, if there are other repo's disable, yum -y update and then do the install process again.
     
    JDConnors, Mar 3, 2014
    #16
  17. sthevan79

    sthevan79 New Member

    what was line ur r missing , will help full if u cloud share it
     
    sthevan79, Mar 3, 2014
    #17
  18. sthevan79

    sthevan79 New Member

    ok thanks for info,let me try out fist
     
    sthevan79, Mar 3, 2014
    #18
  19. JDConnors

    JDConnors New Member

    Did you read what I put in the quotes?

    Regardless, the missing line would not have stopped ISP from working. 99.9999999% sure it was the enabled 3rd party repo.
     
    JDConnors, Mar 3, 2014
    #19
  20. sthevan79

    sthevan79 New Member

    already remove said repo, but when access getting below page only

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <html><head>
    <title>400 Bad Request</title>
    </head><body>
    <h1>Bad Request</h1>
    <p>Your browser sent a request that this server could not understand.<br />
    Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
    Instead use the HTTPS scheme to access this URL, please.<br />
    <blockquote>Hint: <a href="https://redirector-sjl.enom.com:20000/"><b>https://redirector-sjl.enom.com:20000/</b></a></blockquote></p>
    </body></html>
     
    sthevan79, Mar 3, 2014
    #20
Page 1 of 2

Share This Page