problems of ports after upgrading to 3.0.5.1

Discussion in 'General' started by pier56, Mar 2, 2013.

  1. pier56

    pier56 Member

    Hello,

    There were 3 errors like :
    "(98)Address already in use: make_sock: could not bind to address [::]:443"
    With ports 80, 443, 8081.

    The error with port 80 disappeared when I stopped lightppd (which was listening on port 81).

    The error with port 443 disappeared when I removed an extra line "Listen 443" which was added by ispconfig upgrade.

    And after that, apache has started with no error on port 8081 (apps).

    A bug ?
     
  2. Whistler

    Whistler New Member

    Hello!

    I can't assign the "Database user" to some sites in "Databases" part, no users in field. :confused: For some websites it's Ok.

    This issue happened after upgrade from ISPConfig 3.0.4.6 to 3.0.5.1.

    Ubunutu 10.04 LTS Server.
     
  3. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    I don't think this is a bug. As you said, Lighttpd was listening on some ports.
     
  4. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Please open a new thread for this one.
     
  5. Whistler

    Whistler New Member

    I figured out, it was my misunderstanding. Now everything is Ok! Thank you!
     
  6. pier56

    pier56 Member

    Port 80 was freed after lighttpd was uninstalled.

    But port 443 was blocked by an extra line in config file of apache2.

    Now, it works, and if nobody has the same problem, it was a problem just for me...
     
  7. pier56

    pier56 Member

    Hello,


    Same problem with 3.0.5.2, extra line at the end of config file of apache2, ports.conf :

    Listen *:443
    </IfModule>
    Listen 443
     
  8. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    AFAIK, ISPConfig does not touch ports.conf.
     
  9. pier56

    pier56 Member

    Ok, it is not a problem of ispconfig, but a problem of my debian installation which appeared with ispconfig 3.0.5.
    It is easy to correc tmanually, I'll try to understand with next patch.
     

Share This Page