Module not disabled but seems to be disabled

[supportynovbordeaux]

Hello everyone,
I am facing a tricky problem with version 1.5.10.1733 and client 0.13.0. In the logs, I constantly see:

---------------------------------SnapinClient---------------------------------

17/12/2025 09:40:49 Client-Info Client Version: 0.13.0
17/12/2025 09:40:49 Client-Info Client OS: Windows
17/12/2025 09:40:49 Client-Info Server Version: 1.5.10.1733
17/12/2025 09:40:49 Middleware::Response Module is disabled on the host

And indeed, I can't deploy snap-ins; they remain in the QUEUE all the time. I have to disable the snap-ins in services on the group and then reactivate them for it to work and for the queue to clear.

[darksidemilk]

So this is probably not a client issue but a config issue or a server issue.
When you set the module (disable or enable) on the group you're actually bulk enabling or disabling the module per host.
If you can recreate the problem, then get a stuck queue and then go check one host in the fog server gui to see if the snapin service is disabled.

If it is not disabled and you still need to reset it each time something else is going on and we can try and narrow this down.

Are these new hosts or are they long term existing hosts?

[darksidemilk]

I ask if they're new or old because if they're new I'd also be sure that snapins are enabled by default on new hosts in the server config.

[supportynovbordeaux]

Hello,
The activation of snapins globally has always been enabled. I've been using FOG for imaging since the beginning for about 20 years, and I've never had this problem. If I activate the snapins locally on the group, for example, the machines deploy fine but very quickly the issue reappears, and I really don't understand why. The issue appeared starting with version 1.5.10.1733, so I just updated to version 1.5.10.1734, hoping that it’s just a side effect of something else.
Thank you anyway for your response.

[darksidemilk]

I apologize if I offended you with the basic questions, we just always need to rule out the basics and also ensuring that some other recent change in an update didn't break a basic function that got missed, I wasn't trying to insinuate you didn't know to check those things. Your 20 years of use is impressive and appreciated.

If you can answer some more troubleshooting questions I'm sure we can trace this out and get to the bottom of it.

• When the issue happens, do the hosts show snapins enabled on the server for that host, or do they show disabled? (I want to know if the service is correct that the host has it disabled, or is it getting the wrong answer so we can see if the hosts are randomly disabling or the service is getting confused)

• Are these new hosts or existing hosts? (I want to know if the snapins enabled by default is working correctly if they're new hosts, if they're existing hosts, need to figure out what is causing them to disable)

• If they are new hosts, how are you creating them (Web Gui, pxe boot, api, import, etc) ? (I want to trace the right path of creation)

• Do you have any plugins enabled? ( I want to be sure I recreate your environment as close as possible when trying to recreate the issue)

[supportynovbordeaux]

So:

• In the FOG interface, the snapins remain in QUEUE. On the machines, the message is posted.
• These are both old and new hosts without distinction. However, in the interface, the snapins remain activated.
• The hosts are imaged from a master and then deployed via PXE. Once deployed, we add the MAC and a computer entry in FOG, we activate AD. The machine restarts and becomes operational.
  So we have LDAP, Subnet Group, Location, Windows key, Integrity settings, and Access Control. By the way, Integrity settings doesn't report anything...

[darksidemilk]

Did you happen to try restarting the fog service on any of the hosts that were stuck?
Just curious if another workaround exists to get it to push.

@mastacontrola do you think there's a chance that any of the recent token based security things could have affected client communication like this?

[supportynovbordeaux]

I'm curretly updating all hosts (15) to the latest version. I can come back to you if it happens again after the update, can i?

[darksidemilk]

Sounds good, we can wait