Working 1.6 differences and API structure
-
I’m testing FOG 1.6.0-beta (build 2253) on Ubuntu 24.04. A single FOG server that runs also DHCP.
I’m having three related issues:
GET /fog/system/info works fine (returns version and success).
All authenticated routes (like /fog/host or /fog/image) return 403 Forbidden.
API and User tokens are both enabled and verified in the database.
The same API requests work on my production FOG 1.5.10 instance.
The main difference is that this new install uses PHP-FPM (proxy_fcgi) instead of mod_php.
Is there any required Apache config (e.g. header forwarding) for FastCGI so the fog-api-token and fog-user-token headers are passed correctly?
In 1.6, the global API token looks base64 encoded in the web UI, while user tokens look like the old raw hex format.
Are tokens now stored or displayed differently in this version?
Should API requests use the displayed (encoded) token or the raw decoded value?
On the web GUI, I can’t change any values under FOG Configuration → FOG Settings. All values seem hard-coded.
Is this a known issue in the 1.6 beta, or could it be a permissions problem?
Any guidance or clarification from the developers or anyone else using the 1.6 beta would be appreciated.