Nurhak Kaya's Software Development Blog

In order to develop apps using the HTTPS URL on your local machine, you should create SSL certificates.  SSL works by ensuring that any data transferred between users and websites or between two systems remains harder(if not impossible) to read as the data might potentially include some sensitive information, i.e. names, payment details etc. Please read this article for more details.  Creating a development SSL certificate will stop you from seeing the following error when you visit your local IIS website and potentially save you some headaches in the near future as things get more strict with security. There are multiple ways to generate a SSL certificate. I prefer to use Windows PowerShell to generate my local certificates and here is how you can do it; Open up PowerShell and run it as an Administrator Type the following command for your project and hit enter. New-SelfSignedCertificate -DnsName "YOURPROJECTNAME.localhost" -CertStoreLocation "cert:\LocalMachine\My"

If you have started working with Umbraco v9 and done your first Azure deployment to one of your testing environments, there is a possibility that you might see the following "Boot Failed" error. Error: Checking the logs In order to understand the problem, you should check the Umbarco log file.  The default location for this file is umbraco/Logs and this file contains the Machine name, along with the date information. You can reach this file via Azure's Kudu Service  or alternatively, you can get download your Azure App Service's publish profile and connect your App Service via an FTP application, i.e. FileZilla. See the FileZilla screen below; Once you get your log file, you can download it to your local machine and open it with a text editor, i.e. Notepad++. When you open it, you will see all logs, including the error message. Please be aware, as most things with Umbraco, logging is also customizable, so you can either use the default Umbraco logging which is Micros

If your computer goes to sleep and locks your screen after a few minutes and this is not what you have set in your power settings, then this could be due to your "System unattended sleep timeout" settings. In order to see your "System unattended sleep timeout" setting, below is what you can do; Go to advanced power settings Find Sleep>"System unattended sleep timeout" and set the "On battery" and "Plugged in" timeout settings. If you can't see this setting; Open up your "Registry Editor" by running it as an administrator In the file, go to the following location, double click on the Attributes and set the value to 2 and save. This will make the "System unattended sleep timeout" section visible in your Power options window. HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Power\ PowerSettings\ 238C9FA8-0AAD41ED-83F4-97BE242C8F20\ 7bc4a2f9-d8fc-4469-b07b-33eb785aaca0