Posts made by sega

@Tom-Elliott I thought that too but these are the settings from the old PCs. The only thing that is weird here, is that Secure boot is enabled but there is also a “Not active”?

@Tom-Elliott I know when we set up the last Pcs we didn’t install any certificates, just changed some settings in the mainboard and thats it (plus updating the BIOS).
Can you tell me where the certificates could be? Then I could look if there are some on the FOG server.

@Tom-Elliott Thanks for you quick reply.
As far as I know (didn’t installed it) there weren’t any certificates installed.
And, as I read my first post, that could cause a confusion, the old systems still work. So we have both systems currently here and just the old PCs working with the settings.

Hi,

we got a few new pcs and I wanted to get them in FOG too. But with the same BIOS settings as the old pcs I’m getting the following error: Secure Boot Violation. Invalid signature detected. Check Secure Boot Policy in Setup.

The weird thing is: Nearly all options are the same the few different things are (old is the system where FOG is working):
Operating system: Windows 10 (old) - Windows 11 (new)
Mainboard: Gigabyte Z690 UD (old) - Gigabyte Z790 AORUS ELITE AX (new)
BIOS version: F7b (03/28/2022) (old) - F10 (12/25/2023) (new)

All other things are the same as far as I can see. The factory setting of the Secure Boot was on Custom instead Standard but with neither of the both option the PC can’t load FOG. Our FOG version is 1.5.9 and following my information this version should be working with Secure Boot as it does on the old PCs.

Does anyone knows what the problem could it be?

I changed the code to PHP and now it works, so I think it was something security related from the browser.

This should work (worked at the start), but that’s a good point. I will test it with another API just to get sure.
The HTML file just runs on a PHP server but has no PHP in it, just HTML and JavaScript. But won’t be a big problem, to rewrite it in PHP, if that’s necessary.

Ok, the call in Postman worked now, I just had to change a setting.
Now I want to import that call in html/js. But I just get an error as response:

GET http://192.168.xxx.xxx/fog/task/active net::ERR_ABORTED 403 (Forbidden)

I’m pretty sure I have to change something in the fetch function? But I’m not sure. The HTML file is right now running on a local PHP server.

fetch("http://192.168.xxx.xxx/fog/task/active", {
        method: "GET",
        mode: "no-cors",
        headers: {
          "fog-api-token": "token",
          "fog-user-token": "token"
        }
      })

@Tom-Elliott I saw this site also and used the example at the end of the page:

curl -H 'fog-api-token: abcde' -H 'fog-user-token: fghij' -H 'Content-Type: application/json' -X POST -d '{"taskTypeID":13,"deploySnapins":6}' http://fogserver/fog/host/1/task

I used this one, removed the "deploySnapins and changed the taskTypeID into 1, which should stand for the task of deployment. Still the same error. There isn’t any documentation about the various taskTypeIDs, I think thats my main problem.

@Tom-Elliott

The endpoint I’m trying to reach is: http://192.168.0.0/fog/host/128/task
And as I read in the documentation I have to add taskType: 1 as the body. So basically I just need to know which ID the task “Deploy” has.

Hi,

I would like to know if and how it’s possible to limit the brandwith speed for deployment.

Hi,

I’m currently coding a simple-to-use-Webview for my colleagues, it will just contain some buttons to deploy images on hosts/groups. And at this point I have a problem. I want to call the deploy action but I get only this response:

{ "error": "Invalid tasking type passed" }

Followed the documentation on here (https://docs.fogproject.org/en/latest/Knowledge-Base/integrations/api/?h=api#put) so I set the taskType as “1”. I’m testing it in Postman. Other get examples are working, so the token are right.

Does anyone know what’s the problem? Thank you in advance.