If ISPC panel is not reachable.

Discussion in 'General' started by neumann, Feb 7, 2023.

  1. neumann

    neumann Member

    HI
    I have a fairly new install of ubuntu 22.04LTS and ispc 3.2.9 (want to upgrade to 3.2.9p1) but I can't seem to get in contact with ispc webinterface. I thought that I might have done an error in my firewalls (one in ispc and one on the router), but i'm usually not that stupid (anymore :)).
    It is not even reachable on the local network.
    All the sites made from within ispc are fine.

    output from testscript:

    Seems like the ip is lost? How do I fix that?
     
    Last edited: Feb 7, 2023
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig listens on all IP addresses on port 8080 and according to the test script, port 8080 is online with apache:

    *:*:*:*::*:8080 (1179/apache2)

    But you seem to run some additional firewall rules for Docker with ufw, so maybe you blocked it using ufw firewall?
     
  3. neumann

    neumann Member

    That may very well be. I tried to install seafile within ispc from the tutorial "https://www.howtoforge.com/tutorial/setup-seafile-inside-ispconfig/". I used before on my previous server setup, running on ubuntu 18.04 with ispc 3.2.8, and it worked flawlessly. But after trying on the new system it didn't work.
    So somebody here suggested to try to install it with docker, which obviously gives me some resistance.
    I have only tried to install the docker, and have not even tried seafile yet.
    Is it possible to uninstall ufw, and maybe docker, to bring back the functionality of whatever firewall ispc uses?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Instead of uninstalling ufw, try to stop it using systemctl and check if this resolves the issue.
     
  5. neumann

    neumann Member

    I used "ufw disable", and that solved the problem. Before disabling ufw i made a "ufw staus" gave this output:
    Nowhere port 8080 is mentioned. So why could it block port 8080 for ispc? Is it overwriting the rules set by ispc?

    Now that I knew I could make it work again, I made an experiment. Inside ispc i saw that I hadn't opened port 8080. So I tried doing so, and then enable ufw again. And then made a "ufw status" command, and voila, the port 8080 was active, and I can still get in contact with ispc control panel.

    So since I don't know enough about the linux firewall, I make the assumption, that the firewall is a file that can be manipulated/written to by different programs of which ufw is one. Is that file called iptables? Is ispc writing directly in iptables?
    Reading a ltlle about it, I get the assumption that ufw is allready preinstalled on ubuntu 22.04lts. So I assume I haven't broken anything by installing docker, and can disable ufw and rely on ispc to handle the firewall. Am I right?
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    No, ISPConfig uses the ufw command to open and close ports according to the port list you set in ISPConfig under system > Firewall.

    If you had not added port 8080 to the firewall in ISPConfig (it's there when you create a new firewall record by default), then this port is closed and unreachable. By default, when you do not create a firewall in ISPConfig, it is open as well. So not sure if Docker installation had any effect, might be that its unrelated.
     
  7. neumann

    neumann Member

    Hmm. I am pretty sure that I haven't deleted the port 8080, but I have been cleaning up and removed port 8081 and 8082 (which I opened i conjunction with the first installation of seafile). When I removed that, I also cleaned up the firewall, and without remembering, I might have been stupid enough to have closed port 8080 unintentionally. That is ofcause poisonous.

    There remaining question is. Do I leave ufw disabled or should I enable it again now that port 8080 is back and open?
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    I would recommend enabling it again.
     
  9. neumann

    neumann Member

    I will then. Thank you. :)
     

Share This Page