Addon webpage ingress issues because of Firefox’s tracking protection. Eventually got the exception correct.
Forgot about changing some Home Assistant API sensors to http.
Stuffed around for ages with the iOS app trying to get the internal URL right before remembering I had disabled wifi on my mobile to test external access
VSCode sync was generating lots of errors in Home Assistant until I updated the internal URL to http.
The Chormecast URL was indeed the the Nabu Casa URL and that turned out to be easiest thing to fix.
So now I have external access without port forwarding, a smooth sounding Irish lass to do my TTS announcements and I am supporting Home Assistant development. Nice.
EDIT: one, hopefully last, thing I had to clean up. Had to delete my duckdns domain as it was generating these errors:
Logger: aiohttp.server
Source: /usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py:393
First occurred: 16:27:35 (9 occurrences)
Last logged: 19:19:29
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 314, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp/_http_parser.pyx", line 546, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'invalid HTTP method'"
Had to set the logging level to debug to track it down.
Thanks for your quick reply. So is the only solution here to go to Nabu Casa? Or should I just ignore this warning as long as my HA password is strong enough?
I found that I didn’t need the domain at all. Just use the /local folder structure - the domain is added depending on the root you are serving from. The bit I was not understanding was what /local actually meant.