Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
@kratkale Install using
dev-branch -
@Tom-Elliott
fyi:
again no interaction with the web interface - today another PC lost the hostDevice.
root@fog:~/NVME_Problem/hostDevice# ./anzeigen
±---------+
| hostName |
±---------+
| PC102CAD |
±---------+

Yesterday it was PC002CAD today PC102CAD.@Tom-Elliott said in Windows 11 | 65x HP Z2 Tower G1i | UPDATE -:
dev-branch
ok
Your version of FOG is up to date.
You’re running the latest dev-branch version: 1.5.10.1858 -
@Tom-Elliott
since yesterday no devices lost -
@kratkale So things are working under the latest with dev-branch?
-
@Tom-Elliott
at the moment no lost devices. I did my test at the moment. But no cloning - or other tasks - next week I’ll start to test … -
@Tom-Elliott
Problem with upload of a snapin.
First a working snapin stop working:
08.06.2026 15:13:27 Client-Info Client Version: 0.13.0
08.06.2026 15:13:27 Client-Info Client OS: Windows
08.06.2026 15:13:27 Client-Info Server Version: 1.5.10.1858
08.06.2026 15:13:27 Middleware::Response Success
08.06.2026 15:13:27 SnapinClient Running snapin 010_LEHRER_CAD2
08.06.2026 15:13:27 Middleware::Communication Download: http://192.168.0.196/fog/service/snapins.file.php?mac=F8:ED:FC:55:CF:93|0A:00:27:00:00:02&taskid=164
08.06.2026 15:13:31 SnapinClient C:\Program Files (x86)\FOG\tmp\010_LEHRER_CAD2_202404280859.bat
08.06.2026 15:13:31 SnapinClient ERROR: Hash does not match
08.06.2026 15:13:31 SnapinClient ERROR: --> Ideal: 190C52D094C5170B44F32883DEEE59FED0FD5016114B7A64A79EB614BFFBBB39D79B65DB9CE9DE3D0B35FE58AC23B59353D58F190B23CF1F797698055B7D5B44
08.06.2026 15:13:31 SnapinClient ERROR: --> Actual: 6B20738DF050F01FA8E2AAF43235EE959069D2E0ECEA5FE4D7141F802D4F7673E1E51A92F315AE319EC289BA3494047DD006E86371358380FED7A38A9AFB8793
08.06.2026 15:13:31 Middleware::Communication URL: http://192.168.0.196/fog/service/snapins.checkin.php?taskid=164&exitcode=-1&mac=F8:ED:FC:55:CF:93|0A:00:27:00:00:02&newService&jsontry to upload a new Version in the fog gui:
named: 010_LEHRER_CAD2_202606081517.bat

-
@Tom-Elliott
so I cannot use fog in the development branch - I need the snap in - the old one are not working anymore - I cannot upload new one. -
@kratkale Please update the latest dev-branch. Yes I pushed something that had broken this, and then when it was brought to my attention we fixed the problem. To my knowledge this is working again.
As for the actual snapin upload, I’m not aware of any issues there so you may need to look at your username/password for the storage node.
I suspect there’s a special character that got encoded incorrectly, though I’m not 100% sure. This (too) could be a problem we introduced trying to fix a bunch of XSS issues (for security reasons) but you might be able to more simply fix this by just setting the value on the username/password out of the storage node’s fogsettings username/password inforrmation.
-
@Tom-Elliott
still the same problem:

I don’t understand what I should do:
“As for the actual snapin upload, … you might be able to more simply fix this by just setting the value on the username/password out of the storage node’s fogsettings username/password inforrmation.”
where to change? Here?

or here?

I’m afraid of damaging the system. -
@kratkale It’s already not working, so you updating the value on the Storage NOde (your second image there)
Isn’t going to hurt anything.
-
@Tom-Elliott
OK I changed as root on the ssh the password of fogproject to 2FEWI65tfjFk0awFBGw - also in http://192.168.0.196/fog/management/index.php?node=storage&sub=edit&id=1it is still not working …
-
@kratkale I don’t know why you’re telling me your password. (You probably will want to change that now.) and what isn’t working?
-
This post is deleted! -
@Tom-Elliott The Fog server is well hidden behind a firewall
I intentionally sent the password you see there are no special characters in it, and it still doesn’t work.
The old Snap-ins don’t work, and I can’t upload new ones.
It’s all so secure that nothing works!
I’m starting to get a little desperate—I really need to clone again soon… I honestly have no idea what else to do. -
The FOG Password is stored on two places:
Tabelle: globalSettings -> this is unchanged
Tabelle: nfsGroupMembers -> changed …I try now to change in globalSettings by sql and test it again …
-
-
oh I was back again on the stable version
-
-
@kratkale I want to fully understand:
this is after a fresh install/fresh update from the installer and your’e having all these issues?
it seems (at least at first glance) ftp isn’t liked very much.
As for the snapins I’m at a loss. If you’d be daring can you install the branch working-1.6?
This shifts from FTP in preference of actual SSH and might be better. Of course working-1.6 is more or less in “beta” so this is understandable to be hesitant, but at the same time, without enough testing and feedback, little can move the needle closer and closer to RC -> Master.
Even in the age of AI, there’s not enough data (for me at least) to feel comfortable moving it toward master/stable yet so if you’re daring please upgrade to working-1.6
I will highly recommend making a backup or snapshot pre-upgrade to it just in case something is significantly worse.
The error message you got (OOPS: cannot change directory) seems to indicate authentication is now working but ftp is failing because it cannot drop you to the users’ home directory. The why of that I do not know but I do believe this would be fixed in working-1.6 (or at least I’ll have more assistance to troubleshoot things with you as I’m generally working from that branch).
-
@Tom-Elliott
I’ve been using FOG myself for well over 10 years now. With each new generation of PCs (this is now the third), I’ve completely rebuilt the FOG server and then simply used it throughout the PCs’ lifespan. Without any major updates… (never change a running system). The PCs and the FOG server are separated from the rest of the school network by an IPFire firewall. No unknown devices can connect to my network. All allowed MAC addresses are registered on the switch. Access from unknown MAC addresses is not possible.Yes, I’ve been having all these problems ever since switching to the new PCs. First, the NVMe issues (deleting my second hard drive in the system), …
I need to figure something out: school lets out here in a week. At the start of the semester, I’ll have to deploy a new image to the PCs. Right now, nothing is working at all! As things stand, I’ll have to deploy the new image via Clonzilla again and manually install the “necessary snap-ins” on the PCs.
Here’s the process so far:
-) Initial installation on the newly set up Debian system:
git clone https://github.com/fogproject/fogproject.git
-) No snap-ins were directly transferred from the old system; instead, they were re-uploaded, all PCs were re-added, and all groups were reinstalled. In other words, nothing was directly transferred from the old FOG. After encountering problems with the first FOG server (hardware issues—the whole process was repeated with different hardware)
-) After the NVMe issues, I updated the download and reinstalled it:
cd fogproject
git checkout dev-branch
git pullSo yeah, right now I’m trying everything—I’ve got nothing to lose.
I work in a secure environment—FTP and TFTP are old, proven concepts. I’m not really a big fan of making things “even more secure,” and that’s not the point here… I find even the whole thing with the snap-ins’ hash values tedious. Why can’t I just log in to the Fog server via SSH, fix the snap-in, and be done with it? No, I have to upload it again via the web interface… The filename can’t be the same…
The database is now backed up using phpMyAdmin.
cd fogproject
git checkout working-1.6
git pull
userdel fogproject
fogproject/bin/installfog.sh
-
Press [Enter] key when database is updated/installed.
-
Update fogstorage database password…OK
-
Granting access to fogstorage database user…Skipped
-
Setting up storage…OK
-
Setting up and starting DHCP Server…Skipped
-
Configuring default iPXE file…OK
-
Setting up and starting TFTP Server…OK
-
Setting up and starting VSFTP Server…OK
-
Setting up FOG Snapins…OK
-
Setting up UDPCast…OK
-
Configuring UDPCast…OK
-
Building UDPCast…OK
-
Installing UDPCast…OK
-
Installing FOG System Scripts…OK
-
Configuring FOG System Services
-
Setting permissions on FOGMulticastManager.service script…OK
-
Enabling FOGMulticastManager.service Service…OK
-
Setting permissions on FOGImageReplicator.service script…OK
-
Enabling FOGImageReplicator.service Service…OK
-
Setting permissions on FOGSnapinReplicator.service script…OK
-
Enabling FOGSnapinReplicator.service Service…OK
-
Setting permissions on FOGScheduler.service script…OK
-
Enabling FOGScheduler.service Service…OK
-
Setting permissions on FOGPingHosts.service script…OK
-
Enabling FOGPingHosts.service Service…OK
-
Setting permissions on FOGSnapinHash.service script…OK
-
Enabling FOGSnapinHash.service Service…OK
-
Setting permissions on FOGImageSize.service script…OK
-
Enabling FOGImageSize.service Service…OK
-
Setting permissions on FOGFileDeleter.service script…OK
-
Enabling FOGFileDeleter.service Service…OK
-
Setting up FOG Services…OK
-
Creating FOG cache directory…OK
-
Starting FOGMulticastManager.service Service…OK
-
Starting FOGImageReplicator.service Service…OK
-
Starting FOGSnapinReplicator.service Service…OK
-
Starting FOGScheduler.service Service…OK
-
Starting FOGPingHosts.service Service…OK
-
Starting FOGSnapinHash.service Service…OK
-
Starting FOGImageSize.service Service…OK
-
Starting FOGFileDeleter.service Service…OK
-
Setting up NFS configuration file…OK
-
Setting up exports file…OK
-
Setting up and starting RPCBind…OK
-
Setting up and starting NFS Server…OK
-
Ensuring node username and passwords match…Done
-
Setting up FOG External Reporting…Done
-
Setup complete
You can now login to the FOG Management Portal using
the information listed below. The login information
is only if this is the first install.This can be done by opening a web browser and going to:
http://192.168.0.196/fog/management
Default User Information
Username: fog
Password: password -
Changed configurations:
The FOG installer changed configuration files and created the
following backup files from your original files:- /etc/exports <=> /etc/exports.1782208473
- /opt/fog/reporting/report.sh <=> /opt/fog/reporting/report.sh.1782208473
-





