<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting on MichelleWayZ | Michelle Goossens | Blog</title><link>https://blog.michellewayz.com/categories/troubleshooting/</link><description>Recent content in Troubleshooting on MichelleWayZ | Michelle Goossens | Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2019-2026, Michelle Goossens.</copyright><lastBuildDate>Tue, 10 May 2022 20:24:29 +0000</lastBuildDate><atom:link href="https://blog.michellewayz.com/categories/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Terraform error: Service returned an error. Status=&lt;nil&gt; &lt;nil&gt; when creating an Azure Web App</title><link>https://blog.michellewayz.com/azure-terraform-error-status-nill-nill/</link><pubDate>Tue, 10 May 2022 20:24:29 +0000</pubDate><guid>https://blog.michellewayz.com/azure-terraform-error-status-nill-nill/</guid><description>
&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Today I was tinkering around with Azure and Terraform. I’ve been working on creating a Azure Web App based off of Linux. However I ran into the following error:&lt;/p&gt;
&lt;blockquote class="wp-block-quote is-style-plain"&gt;
&lt;cite&gt;Failure sending request: StatusCode=0 &amp;#8212; Original Error: autorest/azure: Service returned an error. Status=&lt;nil&gt; &lt;nil&gt;&lt;/cite&gt;
&lt;/blockquote&gt;
&lt;p&gt;This was caused by two things. Per the docs, the &lt;code&gt;always_on&lt;/code&gt; option should be &lt;code&gt;false&lt;/code&gt; by default, but it actually defaults to &lt;code&gt;true&lt;/code&gt;. Because I was using the F1 SKU, which is free, this failed as it does not support always_on and it must be a 32 bit worker as well so I also set &lt;code&gt;user_32_bit_worker&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt; just to be sure.&lt;/p&gt;</description></item><item><title>VMware Purple Screen of Death troubleshooting for random crashes with disk errors in the homelab.</title><link>https://blog.michellewayz.com/vmware-purple-screen-of-death-troubleshooting-for-random-crashes-with-disk-errors-in-the-homelab/</link><pubDate>Thu, 04 Jun 2020 21:18:52 +0000</pubDate><guid>https://blog.michellewayz.com/vmware-purple-screen-of-death-troubleshooting-for-random-crashes-with-disk-errors-in-the-homelab/</guid><description>
&lt;p&gt;Hi everyone,&lt;/p&gt;
&lt;p&gt;Time for a new blog post about the adventure I’ve been having for the past two days.&lt;/p&gt;
&lt;p&gt;On June 2nd, my server, a DL380G6 started to suddenly take-off. The fans were roaring at 70%, and the temperature sensor near the PCI Riser was showing 110 C. Of course this is not supposed to happen, in this blog post, I will take you through my experience of troubleshooting this and hopefully this can help you.&lt;/p&gt;</description></item></channel></rss>