If you see the following deployment error, it may be due to using a free app service plan and running out of space. To resolve this issue, you can delete old log files (via Kudu) or scale up your app service plan to a non-free option.
Likewise, if you encounter "500 server error strict-origin-when-cross-origin" errors while loading elements such as your Umbraco backoffice, scaling up your free app service plan should also resolve this error.
PS: These are misleading errors.
Error:
2024-07-17T16:43:56.9791667Z ##[error]Error: Error Code: ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
More Information: Could not connect to the remote computer ("project-name-uksouth-uat-202405-web-appservice.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
Error: The remote server returned an error: (500) Internal Server Error.
Error count: 1.
Comments
Post a Comment