Home Assistant - Revision history

KN6DWI: Added instructions for setting up TLS

2026-08-13T18:02:43Z

Added instructions for setting up TLS

← Older revision		Revision as of 18:02, 13 August 2026
Line 19:		Line 19:

	== Optional: Set up TLS ==		== Optional: Set up TLS ==
			If you have a domain name, it can be used with Let's Encrypt and CertBot to easily set up an automatically renewing TLS certificate. If you're running Home Assistant OS, you can use the [https://github.com/home-assistant/addons/blob/master/letsencrypt/DOCS.md Let's Encrypt app]. If you're running Home Assistant in a docker container, apps are not supported, so you'll need to [https://certbot.eff.org/ set up CertBot yourself].

	== Troubleshooting ==		== Troubleshooting ==

KN6DWI: Added verify connection, TLS, and troubleshooting sections

2026-08-13T17:34:42Z

Added verify connection, TLS, and troubleshooting sections

@@ Line 7: / Line 7: @@
 == Step 1: Set up your tunnel ==
 Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel | single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term|bare metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet | routed subnet]].
 == Step 2: Open port ==
@@ Line 15: / Line 13: @@
 * <code>firewalld</code>: <code>sudo firewall-ctl --zone=<wireguard interface zone> --add-port 8123/tcp --permanent</code>
 * <code>ufw</code>: <code>sudo ufw allow 8123 proto tcp</code>

KN6DWI: Added examples for opening the port

2026-08-07T23:26:35Z

Added examples for opening the port

← Older revision		Revision as of 23:26, 7 August 2026
Line 11:		Line 11:

	== Step 2: Open port ==		== Step 2: Open port ==
	Now that your Home Assistant instance and 44Net Connect tunnel are set up, it's time to open the required port in your firewall to make Home Assistant publicly accessible. The default Home Assistant port is 8123, so unless you've changed it, you'll need to open <code>8123/tcp</code> in your firewall. If you're running a single device tunnel with a Home Assistant VM or docker container, it's as simple as opening the device's firewall on <code>8123/tcp</code>. If you have a Home Assistant appliance inside a routed subnet, you'll need to open the port in the router's firewall, and ensure the firewall's rule set allows {{Term\|WAN}} devices to initiate connections on that port.		Now that your Home Assistant instance and 44Net Connect tunnel are set up, it's time to open the required port in your firewall to make Home Assistant publicly accessible. The default Home Assistant port is 8123, so unless you've changed it, you'll need to open <code>8123/tcp</code> in your firewall. If you're running a single device tunnel with a Home Assistant VM or docker container, it's as simple as opening the device's firewall on <code>8123/tcp</code>. If you have a Home Assistant appliance inside a routed subnet, you'll need to open the port in the router's firewall, and ensure the firewall's rule set allows {{Term\|WAN}} devices to initiate connections on that port. The syntax for doing so varies based on your firewall tool.

			* <code>firewalld</code>: <code>sudo firewall-ctl --zone=<wireguard interface zone> --add-port 8123/tcp --permanent</code>
			* <code>ufw</code>: <code>sudo ufw allow 8123 proto tcp</code>

Airgapped at 20:10, 7 August 2026

2026-08-07T20:10:10Z

← Older revision		Revision as of 20:10, 7 August 2026
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|~~Bare~~ metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|bare metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped at 20:06, 7 August 2026

2026-08-07T20:06:37Z

← Older revision		Revision as of 20:06, 7 August 2026
Line 1:		Line 1:
	Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, ~~{{Term\|Bare}}~~ but cannot port forward due to {{Term\|CGNAT}}, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.		Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, but cannot port forward due to {{Term\|CGNAT}}, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.

	Prerequisites:		Prerequisites:
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped at 20:05, 7 August 2026

2026-08-07T20:05:27Z

← Older revision		Revision as of 20:05, 7 August 2026
Line 1:		Line 1:
	Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, but cannot port forward due to {{Term\|CGNAT}}, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.		Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, {{Term\|Bare}} but cannot port forward due to {{Term\|CGNAT}}, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.

	Prerequisites:		Prerequisites:
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]]. ~~{{Term\|bare}}~~		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped at 20:04, 7 August 2026

2026-08-07T20:04:50Z

← Older revision		Revision as of 20:04, 7 August 2026
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]]. {{Term\|bare}}

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped at 20:03, 7 August 2026

2026-08-07T20:03:27Z

← Older revision		Revision as of 20:03, 7 August 2026
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|~~bare~~ metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped: Undo revision 2822 by Airgapped (talk)

2026-08-07T19:44:06Z

Undo revision 2822 by Airgapped (talk)

← Older revision		Revision as of 19:44, 7 August 2026
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|~~Bare~~ metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|bare metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts

Airgapped at 19:43, 7 August 2026

2026-08-07T19:43:53Z

← Older revision		Revision as of 19:43, 7 August 2026
Line 6:		Line 6:

	== Step 1: Set up your tunnel ==		== Step 1: Set up your tunnel ==
	Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|~~bare~~ metal}} , the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].		Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel \| single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term\|Bare metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet \| routed subnet]].

	For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts		For fresh installations using a single device tunnel, it's recommended to configure WireGuard as a {{Term\|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>. This puts