AutomateAPI Connect-ControlAPI throws 500 Internal Server Error

It looks like the 22.2.x.x Control server series may have broken connectivity. Now when I go through the authentication process, the result reads:

Exception: C:\Users\[xyz]\Documents\PowerShell\Modules\AutomateAPI\1.1.4\Public\Connect-ControlAPI.ps1:193
Line |
 193 |  …             Throw "Attempt to authenticate to the Control server has  …
     |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Attempt to authenticate to the Control server has failed with error Response status code does not
     | indicate success: 500 (Internal Server Error).

I just updated the server again to the latest release (v22.2.7294.8116) and getting the same result.

Apr 07 '22 19:04 LittleGreyDuck

Did you get this resolved? I have been using the module across many upgrades (well into 2023 versions) without issue. I am using the APIKey authentication method though, not username/password.

Oct 27 '23 05:10 DarrenWhite99

When I did an OS reinstall, something kicked loose and I was able to get in again. Mind you, Automate and ScreenConnect (hooray for un-re-branding) have moved enough along that things aren't great, like the RepairResult content basically returning "No result was returned" for every endpoint I try to remediate.

Oct 27 '23 16:10 LittleGreyDuck

Wanted to update everyone that we are also having this issue. The script does appear to succeed though as you can see in control that the commands were run and agents were brought back online. If anyone has a fix that would be great.

Thank you for the script.

Dec 19 '23 20:12 mayflowertech