How can I get HTTPS working behind CGNAT? I want to use homeassistant cast to display Lovelace card on Chromecast enabled tv.

[Quick and Easy SSL Certificates for Your Homelab!] how to modify this method for local HTTPS certificate? ============================ Worked for me https://theprivatesmarthome.com/how-to/set-up-nginx-proxy-manager-in-home-assistant/

Anything besides it? I am using both zero-tier and Tailscale for remote access both excellent free solutions, how can I use anyone of those for https access?

You can’t use a VPN like tailscale from a Chromecast

I need a free solution bcz can’t pay 5USD when USD:PKR rate is already rising beyond our reach due to the political situation in the neighbouring country.

So you want to cast your HA to any chromecast, anywhere?

no I just want to cast HA to my local Chromecast enabled TV.

Then, unless mistaken, CGNAT is irrelevant. Just use your local IP. You just need to enable SSL on your HA.

You need a domain for Let’sEncrypt though.

I guess. You can use duckdns+letsencrypt add on to get the certificate generated. Then you would have to tinker with your local DNS to point the *.duckdns.org to your local IP.

Can’t use duckdns behind CGNAT. Oh… you can set it up though. It would just be useless for remote access.

Home Assistant Community

HTTPs behind CGNAT

Configuration

anon11644107 September 14, 2021, 8:09am 8

Hass.io Add-on: Webhook Relay - webhook forwarding & remote access Home Assistant OS

Hass.io Add-on: Webhook Relay Fast & simple reverse tunnels for your Home Assistant. [image] About Webhook Relay addon enables Home Assistant and any other services running inside internal network to receive webhooks from public services such as IFTTT, Zapier, Mailgun or pretty much anything. Add-on also allows you to create bidirectional tunnels for remote access (for example your browser). It works by opening a connection to the public cloud service and giving you your unique “webhooks in…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled