<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web Apps on Thaddeus Koenig</title><link>https://www.thaddeuskoenig.com/tags/web-apps/</link><description>Recent content in Web Apps on Thaddeus Koenig</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Thaddeus Koenig</copyright><lastBuildDate>Thu, 16 Jan 2025 06:06:24 -0500</lastBuildDate><atom:link href="https://www.thaddeuskoenig.com/tags/web-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>400: Bad Request in HomeAssistant</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_400_bad_request_ha-copy/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_400_bad_request_ha-copy/</guid><description>&lt;p&gt;So for some reason in v2021.7.0 HomeAssistant introduced a bug that breaks a lot of systems that rely on its NGINX reverse proxy add-on to provide ssl capabilities. Thankfully the fix itself is pretty simple.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;To begin, try to navigate to the site to produce the error, then in the HAS web GUI navigate to the Supervisor Logs (&lt;strong&gt;Settings&lt;/strong&gt;&amp;gt;&lt;strong&gt;System&lt;/strong&gt;&amp;gt;&lt;strong&gt;Logs&lt;/strong&gt;)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Grab the IP that shows up in the error that reads&lt;/p&gt;</description></item><item><title>400: Bad Request in HomeAssistant</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_400_bad_request_ha/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_400_bad_request_ha/</guid><description>&lt;p&gt;So for some reason in v2021.7.0 HomeAssistant introduced a bug that breaks a lot of systems that rely on its NGINX reverse proxy add-on to provide ssl capabilities. Thankfully the fix itself is pretty simple.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;To begin, try to navigate to the site to produce the error, then in the HAS web GUI navigate to the Supervisor Logs (&lt;strong&gt;Settings&lt;/strong&gt;&amp;gt;&lt;strong&gt;System&lt;/strong&gt;&amp;gt;&lt;strong&gt;Logs&lt;/strong&gt;)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Grab the IP that shows up in the error that reads&lt;/p&gt;</description></item><item><title>VMware Vmmod/VMnet Install</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_vmware_vmod_install/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_vmware_vmod_install/</guid><description>&lt;p&gt;After upgrading my Ubuntu Version and subsequently my kernel I tried running VMware Workstation Pro so I could access my VMs and kept running into the following error code when trying to open the application. Unfortunately, there was no way around it as rebooting, uninstalling/reinstalling, and anything else in my usual low-hanging fruit bag of tricks didn&amp;rsquo;t work so I had to really figure out what was really going on. Lets start with the actual error.&lt;/p&gt;</description></item></channel></rss>