Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    13k Topics
    115k Posts
    K

    @Tom-Elliott
    Unfortunately, the “Reset Encryption Data” feature doesn’t work very well for me. Right now, it seems like I have to press the “Reset” button during the cloning process every time I clone a PC. If I don’t, the Fog Client doesn’t work, and I have to go to the PC in person.
    To make sure the PCs are still usable, I’ve moved the steps for renaming the PC, connecting it to the domain, and installing the Veyon Client to c:\windows\Setup\Scripts\SetupComplete.cmd. This makes the cloning process go more smoothly for me. I also install the Fog Client at the same time.

    Despite all these efforts, I’m not getting anywhere:
    01.07.2026 18:34:53 Middleware::Communication Download: http://192.168.0.196/fog/management/other/ssl/srvpublic.crt
    01.07.2026 18:34:53 Middleware::Authentication Cert OK
    01.07.2026 18:34:53 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
    01.07.2026 18:34:53 Middleware::Authentication ERROR: Could not get security token
    01.07.2026 18:34:53 Middleware::Authentication ERROR: Die Datei “C:\Program Files (x86)\FOG\token.dat” konnte nicht gefunden werden.
    01.07.2026 18:34:53 Middleware::Communication POST URL: http://192.168.0.196/fog/management/index.php?sub=requestClientInfo&authorize&newService
    01.07.2026 18:34:53 Middleware::Communication ERROR: Failed to POST data
    01.07.2026 18:34:53 Middleware::Communication ERROR: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
    01.07.2026 18:34:53 Middleware::Response Success

    01.07.2026 18:34:53 Client-Info ERROR: Failed to authenticate, will not run Module Looper.

  • Get the latest news on what's happening.
    Security Advisories
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2k Topics
    19k Posts
    V

    Hello everyone,

    I am facing an issue with image capturing after performing an upgrade on my FOG server from 1.5.10 to 1.5.10.1886. Before the update, everything worked fine for me. The images were stored directly on the Synology NAS.

    My Setup:

    FOG Server: IP 192.168.10.220 (Debian 13) Storage: External Synology NAS with multiple virtual IPs (192.168.109.220 and 192.168.110.220). Storage Configuration: The Synology NAS is configured in FOG web UI as the Master Node for its storage group. The local Default storage node is NOT the master. Clients: Multiple clients on different subnets (e.g., 192.168.109.23 and 192.168.110.23).

    The Problem:
    The Partclone phase finishes successfully on the client machine. The image files are correctly uploaded via NFS directly to the Synology NAS into the /images/dev/[MAC_ADDRESS] folder.

    However, right after Partclone reaches 100%, the task gets stuck in the FOG Web UI (at around 70%), and the client screen shows the following PHP FTP error:

    Error returned: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 709, Message: ftp_put(/images/dev/[MAC]): Failed to open stream: No such file or directory, Host: 192.168.110.220, Username: foguser

    What I have verified:

    I tested the FTP connection manually via CMD/PowerShell from a PC using the same foguser credentials. I am able to log in, mkdir, rename, and rmdir inside the /images and /images/dev directories on the NAS without any permission errors. If I move and rename the MAC folder manually inside Synology File Station from /images/dev/[MAC] to /images/[Image_Name], the image works fine. This setup worked flawlessly before the FOG server upgrade. The /images directory is NOT mounted locally on the FOG server itself (and never had to be). Verified FTP username and password on NAS and FOG. It's same.

    It seems that fogftp.class.php is incorrectly triggering ftp_put (trying to read a local file from the FOG server) instead of doing a remote ftp_rename directly on the NAS storage node.

    Has anyone encountered this bug after a recent upgrade, or is there a specific setting in the new version that I missed?

    Thank you for any help.

    Storage Node for NAS
    Storage Node for NAS.png

    Error on PC
    U10-PC13.jpg

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    K

    @Valer Hi Valer,

    You can see my tutorial on using Secure boot with Shim, and my thoughts on what 2.0 means for Secure Boot with FOG here: http://forums.fogproject.org/post/158170

89

Online

12.7k

Users

17.6k

Topics

156.7k

Posts