DNS Name Goes to Old FOG Installation

[RobTitian16]

@ITSolutions Windows 10 Pro with Google Chrome. I’ve already attempted to clear my browser history, cookies, etc. to no avail.
The server is Windows 2008 R2.
I do get the correct IP when I ping Fog-server.

Another thing to note is that when I go to the ‘wrong’ login page, I can’t login using any of my credentials. It keeps saying username/password is incorrect.

[ITSolutions]

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

Windows 10 Pro with Google Chrome. I’ve already attempted to clear my browser history, cookies, etc. to no avail.
The server is Windows 2008 R2.
I do get the correct IP when I ping Fog-server.

Another thing to note is that when I go to the ‘wrong’ login page, I can’t login using any of my credentials. It keeps saying username/password is incorrect.

Can you try with IE or Firefox? I have had issues with Chrome using some hidden DNS stuff or something. Not sure how chrome handles DNS, but I had a case that in a school I worked at DNS was having an issue and user couldn’t get to a testing site, but in chrome they had no issue.

[RobTitian16]

@ITSolutions I’ve tried with IE and Edge. I’ll have to download Firefox if you think it’s worth trying on there as well. I still get the same issue. It’s as if 10.1.0.102 goes directly to the right log-in page, whilst the fog-server/fog/management/ goes to an old database or something… like a remnant of the upgrade.

Another thing to note (which is also a bit of an issue but I’m not too bothered about it) is that I edited the Apache settings before upgrading to trunk so that fog-server/ would go directly to the fog-server/fog/management/ page. Since updating to trunk, that’s stopped working.

[ITSolutions]

@RobTitian16 Something that I forgot to ask is what OS is FOG running on?

[RobTitian16]

@ITSolutions Ubuntu 14.04… Perhaps it’s time to upgrade?

[ITSolutions]

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

@ITSolutions Ubuntu 14.04… Perhaps it’s time to upgrade?

No definitely don’t upgrade Ubuntu broke a lot of things in 16.04, so 14.04 is a better choice for now. Ubuntu moved the default location for web pages in 14.04 from /var/www to /var/www/html. FOG is designed to do a symlink back to /var/www, but maybe something broke in that. Can you check to see if there is a /var/www/fog folder and a symlink /var/www/html/fog?

[RobTitian16]

@ITSolutions I can confirm both folders are there and there is a symlink between the two.

[ITSolutions]

What version of trunk do you have? If it is below 7971 can you try updating? This version was just released.

[ITSolutions]

@RobTitian16 Is this a new install of FOG trunk or an upgrade, I guess I am a little confused re-reading your OP.

[RobTitian16]

@ITSolutions Sorry, it’s an old version that was released last week that I’m currently using. I’ll update to the latest and let you know how I get on.

[ITSolutions]

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

@ITSolutions Sorry, it’s an old version that was released last week that I’m currently using. I’ll update to the latest and let you know how I get on.
Did you upgrade the server from 1.2 or did you build a new server and is it the same IP?

[RobTitian16]

@ITSolutions I upgraded the server from 1.2. I can confirm I’m now running build 7971. However, I’m still experiencing the same issue.

[Wayne Workman]

@ITSolutions said in DNS Name Goes to Old FOG Installation:

Ubuntu moved the default location for web pages in 14.04 from /var/www to /var/www/html. FOG is designed to do a symlink back to /var/www, but maybe something broke in that.

I think that statement there is what’s going on.

So, if you use the host name, you are taken to 1.2.0 interface, but if you use the IP you are taken to fog trunk interface.

This means that the web files for 1.2.0 obviously still exist, and the trunk files are there too.

If it were me, I’d delete everything in /var/www EXCEPT for the html directory, and I would delete everything INSIDE of /var/www/html and re-run the installer. That should fix it.

So for instance if you saw some-folder inside /var/www you’d do rm -rf /var/www/some-folder That’s a recursive delete command. same goes for everything in the other.

You can list the contents of the directory, including hidden files, with ls -la

[RobTitian16]

@Wayne-Workman That’s solved it! Thanks a lot for your help