Hi Sanne Dejong,
To fix this, administrators should use Remote Desktop PowerShell tools to verify deployment settings, ensure the SSL certificate has a valid private key with proper Network Service read permissions, and confirm that all URIs match. If the backend configuration is correct, the problem may be caused by corrupted client-side cached scripts, which can be resolved by clearing the browser cache or redeploying the web client packages on the IIS server.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN