After update to latest dev version Apache doesn't respond to hostname
-
I am running the latest dev version on Ubuntu 18.04 and it is no longer responding to the alias in the apache config. I can access the page via the IP address, but we have the hostname entered into all of our clients so this is pretty key to keeping things communicating with the server.
-
@astrugatch said in After update to latest dev version Apache doesn't respond to hostname:
I can access the page via the IP address
This sounds like a dns issue and not a fog issue if you can access it via ip address.
from a windows command prompt key in
nslookupand the name of the fog server and thennslookupand the ip address of the fog server. -
But if I roll back to the snapshot I take before the update it responds to the dns name. nslookup resolves fog.domain.org to 10.10.70.4 as it should. The record is a static A record in our local DNS server (active directory domain).
-
@astrugatch From which version to which do you upgrade? Probably upgrading to 1.5.9.111 but from 1.5.9.X?!?
As far as I know from the top of my head we haven’t changed anything in what we generate into the Apache config recently. But be aware that every time you upgrade/re-run the installer it overwrites the Apache site config. So if you have custom modifications…
-
@astrugatch The other idea I just had: Do you run Ubuntu updates every now and then? If not the FOG installer will do that and there might be some system package update breaking things.
-
Going from 1.5.9.98 to 1.5.9.111.
The fog server gets weekly updates via Landscape so unless entirely new packages get installed somewhere between those two version I doubt that is it. I’m going to snapshot, pull the config from .98 and run the upgrade and compare the two configs to see if anything stands out
I also upgraded rather recently from 1.5.8 to 1.5.9.98 without issue.
-
@astrugatch said in After update to latest dev version Apache doesn't respond to hostname:
Going from 1.5.9.98 to 1.5.9.111.
Here’s the diff between those two versions: https://github.com/FOGProject/fogproject/compare/e34d5a7f152051af3679960e0560a6a911a5292e..ddb9904a7cd56089c6660d1bfdb25af6265282b4
Nothing I would think can break what you see.
-
Finally got a chance to run the upgrade again and figured out my issue.
For some reason safari wasn’t happy with the upgrade. I can open fog fine from a private window or if I cleared history. It doesn’t open in Chrome, which was my other test because chrome doesn’t trust the ssl cert and no longer gives an option to bypass by default.
