Nurhak Kaya's Software Development Blog

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#ERRO

When you clone a remote repository using HTTPS, Git will prompt you for your username and password during the authentication process, on the other hand, when using SSH, Git uses your SSH key to authenticate, which means you don't need to send your credentials over the network.  Furthermore, SSH is a more secure method for cloning repositories, and working with the Git repos, as only the machines with the key file on disk can access these repositories. Even if the SSH key file was to be stolen, it wouldn't give access to the account itself (unlike the credentials) and can be easily revoked.  Creating an SSH Key To generate a new SSH key, open up your terminal app, i.e., Git Bash, and type the following; AzureAD+NurhakKaya@WAT607 MINGW64 / $ cd .ssh/ AzureAD+NurhakKaya@WAT607 MINGW64 /.ssh $ ls id_rsa  id_rsa.pub AzureAD+NurhakKaya@WAT607 MINGW64 /.ssh $ ssh-keygen -t rsa -b 4096 -C "[email protected]" Generating public/private rsa key pair. Enter file in