@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?

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:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp59s0f1:
      dhcp: no
      addresses: [10.50.0.218/24]
      gateway4: 10.50.0.1

I am able to ping 10.50.0.218 with no packet loss, but when I attempt to go to 10.50.0.218 or 10.50.0.218/fog/management 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!

@george1421 Interesting. Thank you for that info. I have only ever done Quick Registration with FOG which seems to identify and register the hosts by their MAC addresses. I figured since FOG was handling DHCP and assigning IPs to MAC addresses anyways (is this even how it works?), it wouldn’t need DNS.

So it uses the MAC addresses as a DNS name?

@george1421 Thanks for the reply! That info is helpful. I am currently integrating a separate FOG server at my work. The first one was set up by someone who doesn’t work here anymore and it has a DNS server.

But even if FOG is on an isolated imaging network, I’m still struggling to understand why DNS would matter? What would it possibly need DNS translations for?

Please excuse my ignorance as I am fairly new to servers/networking in general, but why would FOG need a DNS server if it’s set up for just local imaging? Isn’t it just assigning MAC addresses to IP via DHCP and pushing the image that way? Why would FOG need to translate IPs into domain names and vice versa? Is it for the FOG dashboard maybe?

Thanks all!