Solved Updated from Fog v1.50 to V1.52 issue

[george1421]

@wouwie I see from your post that you are running Debian, wll you also confirm the existence of the file I referenced?

[wouwie]

I have the same issue with the web page but everyting else works fine.
How to fix this?

[george1421]

@bigsease30 For full disclosure I’m a RHEL guy, but I do have fog 1.4.4 running on a raspberry pi in my home.

There should be a file in /etc/apache2/sites-enabled called 001-fog.conf. That file should contain apache directives for the FOG site.

NameVirtualHost *:80
<VirtualHost *:80>
    KeepAlive Off
    ServerName {fog_server_ip}
    DocumentRoot /var/www/
    <Directory /var/www/fog/>
        DirectoryIndex index.php index.html index.htm
    </Directory>
    RewriteEngine On
    RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
    RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d
    RewriteRule ^/(.*)$ /fog/api/index.php [QSA,L]
</VirtualHost>

The rewrite rules are what forward the requests from / to /fog

[Bigsease30]

@george1421 Correct, The GUI seems to work when I am logged in and navigating around if I open it by the IP/Fog addres but the PXE portion is not working. I am assuming that they are related.

[george1421]

@bigsease30 So just to be clear, if you enter the /fog path FOG works OK, its just the redirect from / to /fog that is broken?

[Bigsease30]

Thanks for the reply George. To answer your question, Nothing else was running on the Fog Server. I decided to run an update and it downloaded the newest Ubuntu 18.04 . This didn’t work either so I formatted the drives.

I then reinstalled Ubuntu 16.04, Then installed the newest Fog 1.52 and received the same results as before. I bet something else is going on.

[george1421]

Are you using the fog server for anything else other than FOG?

Your screen shot tells me that something happened to the apache configuration. There was one major change between 1.5.0 and 1.5.2 was enabling php-fpm (a dedicated php execution engine). This has caused centos 6.9 issues, but I don’t think that is your case. This looks more like an apache configuration issue.