SOLVED Static IPs/DHCP, and dashboard not working after FOG installation

  • My colleague and I are having difficulty getting our FOG server dashboard to generate and we’re wondering if it may be something with our current Static IP/DHCP setup.

    We just installed FOG on Ubuntu Server LTS and we wanted to reserve the IP address(es) of the nodes to be static IPs. We are adding this FOG network to an already existing business network connection and we are not using FOG for DHCP and we wanted to defer to our regular DHCP server for the office. Sorry if this is a dumb question, but can we set static IPs on the computer side or would it need to be done on the DHCP server side?

    We ran sudo nano 01-netcfg.yaml and our netplan is as follows:

      version: 2
      renderer: networkd
          dhcp: no
          addresses: []

    I am able to ping with no packet loss, but when I attempt to go to or in a web browser I get no connection. Isn’t the dashboard managment link supposed to automatically generate once installation is complete? What could possibly be going on here?

    Thanks all!

  • Moderator

    @danieln So if you key in does it display any page or error message? Displaying the default apache page is great. That tells you the web server is installed and operational.

  • @george1421 Thanks for that info!

    So, disabling the Ubuntu firewall shows Apache2 Ubuntu Default page showing that it works. It is stating "This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. "

    But still no fog managment dashboard page. This would be the WEB_SERVER right? Doesn’t it automatically generate this at setup?

  • Moderator

    First let me say I don’t know much about ubuntu.

    But from a linux standpoint what you get when you key in sudo ip addr show Also with ubuntu the firewall is turned on by default. Try disabling the ubuntu firewall ‘ufw’ and see if you get a different response.

    Also if you key in sudo netstat -an |grep :80 should show you if the web server is listening on port 80.