I have three groups. I wanted to process group ID==3

curl -vvv --header “Content-Type: application/json” --header “fog-api-token: <my_token>” --header “fog-user-token:<my_token>” -X POST http://<IP>/fog/group/3/multicastsession

< HTTP/1.1 501 Not Implemented
< Date: Tue, 12 Sep 2017 11:25:28 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.31
< X-Powered-By: PHP/5.6.31
< X-Frame-Options: sameorigin
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Strict-Transport-Security: max-age=31536000
< Content-Security-Policy: default-src ‘none’;script-src ‘self’ ‘unsafe-eval’;co
nnect-src ‘self’;img-src ‘self’ data:;style-src ‘self’ ‘unsafe-inline’;font-src
‘self’;
< Access-Control-Allow-Origin: *
< Content-Length: 0
< Connection: close
< Content-Type: application/json
<

• Closing connection 0

@Wayne-Workman
Thx, I’ve tried this, and there is no any action
I have no error but task is not being created.
curl --header “Content-Type: application/json” --header “fog-api-token: <my_token>” --header “fog-user-token: <my_token>” --data ‘{“taskTypeID”:8}’ -X POST http://<IP>/fog/group/3/multicastsession

@Wayne-Workman Hi, thx but " " are needed. I think they depends on the curl version(I’m on WIndows). Without “equals” I got “can not resolve host” error. Moreover, my command gets proper response from the server that tasking type is invalid. I assume API does not support multicast yet. Please confirm that. If you have something not committed to repo yet, please do commit it, as I can test it. Doing CI integration through Jenkins now

May u please validate my curl command?
I keep getting same error as I mentioned few months ago.
{
“error”: “Invalid tasking type passed”
}

I’m trying to task multicast process.

curl --header “fog-api-token: <token>=” --header “fog-user-token: <token>=” --data ‘{“taskTypeID”:8}’ -X POST http://<IP>/fog/group/2/task

@george1421 Thank you. I have 1.4.2 . Do you maybe know if there are some changes in API between my version and 1.4.4 ?
https://news.fogproject.org/fog-1-4-4-officially-released/ keeps popping out 502 error

HI,
Are there any news regarding API implementation?
I wanted to read changelog of RC versions, but keep getting 502 Bad Gateway.
Andrew

O’right
Got it here.
https://news.fogproject.org/simplified-api-documentation/
Perhaps, it should be included on the wiki…

EDIT:
Hmmm. I think that it would be nice to have some multicast deployment examples.
DOcs are missing this information.
I’m getting
{
“error”: “Invalid tasking type passed”
}
whilst I use proper ID=8 for multicast

@Wayne Workman
Thx, but did I miss some API documentation?
I was looking for it here and on the wiki, but found nothing.

It is my second post with workaround today
Here is my working solution to execute deploy task for host with ID=2 from commandline.
So, Jenkins support is not a problem from now on.
I used curl with cookies file to achieve that.

curl -c cookie.txt --request POST --url "http://<your_IP>/fog/management/index.php"  --header "content-type: multipart/form-data"  --form "uname=fog" --form "upass=password" --form "ulang=English" --form "login=Login"
curl -b cookie.txt --request POST --url "http://<your_IP>/fog/management/index.php?node=host&sub=deploy&id=2&type=1" --header "content-type: multipart/form-data" --form "wol=on" --form "scheduleType=instant" --form "taskhosts[]=2"

I had the same issue and after some amount of trials I found the solution.
You have to use external PsExec program from Sysinternals.
You have to create snapin pack and include 2 files- a batch file and psexec.exe one.
PsExec.exe -i -s -u %COMPUTERNAME%\<username> -p <user_password> -nobanner -accepteula REG DELETE “HKLM\SOFTWARE…” /v <some_key> /f
PsExec.exe -i -s -u %COMPUTERNAME%\<username> -p <user_password> -nobanner -accepteula REG ADD “HKLM\SOFTWARE…” /v <some_key> /d <some_value> /f