I get the usual WS Remoting error after changing something at microsoft software. i checked all known parameters from CloudPanel and everything is ok. Is there any known issue due to CU8?
Thank you
I get the usual WS Remoting error after changing something at microsoft software. i checked all known parameters from CloudPanel and everything is ok. Is there any known issue due to CU8?
Thank you
Exchange updates will sometimes reset your powershell virtual directory and leave off the basic authentication flag which you are using for CloudPanel. You will need to enable it again
Thank you for your replay, Jacob.
I had checked that flag already. Basic Auth is still activated. I will get into the issue. If there is no known issue in CU8, I will find a solution.
@iwen65 I will double check all our environments but pretty sure we have some running CU8 already. Also CUs don’t usually have breaking changes which can cause an issue like what you are experiencing
We tested Exchange 2019 CU8 this morning and didn’t have issues connecting to Exchange. This issue is usually one of these two things: https://kb.knowmoreit.com/docs/troubleshooting/the-winrm-client-sent-a-request-to-an-http-server-and-got-a-response-saying-the-requested-http-url-was-not-available/
@jdixonThank you for your help! You are right, the CloudPanel AppPool User was changed to LocalSystem. CloudPanel works reliable and strong as usual again. Top product and support.
