I am running the FOG 1.6 working branch on Ubuntu with Apache.

Current server details:

• FOG branch: working-1.6
• Commit: 47ea627c9
• Database schema: 436
• Apache: 2.4.66
• New client: fog-agent 0.1.6 x64
• Windows 11 clients

The new agent is installed with this server address:

https://192.168.1.100/fog

fog-agent status shows:

{
“enrolled”: false,
“has_key”: true,
“host_id”: 0,
“server”: “https://192.168.1.100/fog”
}

The Windows client is definitely reaching the server.

Apache access log:

192.168.102.20
POST /fog/agent/v1/enroll HTTP/1.1
308
Go-http-client/1.1

A manual test from the FOG server gives the same result:

POST https://192.168.1.100/fog/agent/v1/enroll

Response:

HTTP/1.1 308 Permanent Redirect
Location: https://192.168.1.100/fog/management/index.php

I already re-ran installfog.sh successfully.

The active Apache vhost contains:

<Location /fog/agent/>
SSLOptions +StdEnvVars +ExportCertData
</Location>

and:

RewriteRule ^/fog/(.*)$ /fog/api/index.php [QSA,L]

Apache is listening on 443 and apache2ctl -S shows:

*:443 fog (/etc/apache2/sites-enabled/001-fog.conf:38)

The issue remains after re-running the installer.

Additional information:
The legacy FOG Client 0.13.0 clients on the same server also recently stopped authenticating properly. They repeatedly call:

/fog/management/index.php?sub=requestClientInfo&authorize&newService

but do not continue normally.

Before the recent working-1.6 updates, the legacy clients were communicating normally.

I would prefer an upstream fix rather than manually modifying Apache or PHP files.

Is this a known regression in the current working-1.6 branch affecting the fog-agent /agent/v1/enroll route or the API router?

Thank you.