EDIT: I would like to point out that I did advise Evert (twice) that specifying an external address fot the port forwarding would never work eg : -
Hmmm, wanna bet he uses Nabu casa.???
How did you get on with using your neighbours WiFi to access ?
You are at the limits of my knowledge / experience on this subject now, all I can say is my port forwarding is TCP only and leaves the external address blank. From here on in I think you are breaking new ground. Here is a map of the area you will be travelling through, its blank so just fill it in as you go along
Seriously, if you find out anything more on this report back and I’ll update the thread.
Well thanks Muttley.
Neighbourswi-Fi was a nogo too. I do get to see the frontend but that’s it. So i am knocking at my own door for sure but noone is opening it.
I will adjust my portforwarding by leaving the external IP blank. Just to give it another try.
If that doesn’t work either i will just continue my quest, and i will keep you posted on my progress.
This is something so many people are struggling with. I just cant understand why there is no clear guideline from the DuckDNS or HA devs…Yes i know it is impossible to cover all routers but at least it should be clear which port(s) need to be forwarded to which port(s).
Anyway i won’t give up. It;s way too much of a learningcurve for me although it does consume a hell of a lot of time…
One important note:
I have 2 routers at home: first (router1) is from provider and it does nothing more than passing internet to my another router (router2). To that router2 all my devices are connected including hassio.
So to make DuchDNS work I needed to add port forwarding rule on the router1. It is for 443 to router2 IP.
As a result the connection chain is the following: request comes to the router1 -> router1 forwards it to the router2 -> router2 passing it to hassio.
Hopefully it will save some time for people with multiple routers.
OK to help others out as well: I have fixed it for my configuration…its working!!!
And yes, be sure to read this entire topic!
After following the Mutt step by step guide i still couldn’t get it to work. Then i found out i had a setting wrong in m routers’ portforwaring. Instead of just filling in ext port 443 and forward it to my local IP port 443 i entered my external IP as well and that is where it all went wrong. Removed the External IP and since then it working like a champ!!!
I go backwards and forwards on this external access malarkey…
I know just enough to make it dangerous to open a port but not enough to be sure I am doing it safely.
I am currently toying with Nabu Casa but that seems to have it’s own small can of worms (for me).
Has anyone (ahem, Mutt) ‘peer reviewed’ the above blog post*? It seems to have boiled this very long and now quite complicated and hard to follow thread down to a few simple steps.
*(No disrespect meant @santik, this is more an indication of my concern with opening my system to ‘The World’.)
Sorry klogg, I’ve other things on my plate right now.
I understand your point and it is valid
But I need to work up the interest and have the time to review and possibly test
I have a very interesting issue with Duck DNS using the add store (running supervisor via virtual box on Mac). No matter what I do the config will not save, it just reverts to default (see screenshot). I am totally lost as to why this happens (nothing appears in the logs or in the browser console). I have tried on multiple Macs with different browsers and it keeps doing the same thing. I have installed and uninstalled and rebooted. I can’t see this add-on as a docker container in porntainer (I installed this as per the guide in supervisor and unhide all the container). Other add-ons let me edit the config fine.
Wondering if via terminal I could edit the file manually and then check out the file permissions (as I think that might be the issue here)? I have no idea where this file lives currently.
Thanks @DavidFW1960, I copied the config from the post you linked and it worked! Wow I have no idea why the config pages do not have any error handling (makes it so hard to new users to work out). How would I give feedback to the dev team to look at making these easier for others in the future?
That’s why so many of the solution threads contain ‘examples’ of what worked.
Including the solution post in this thread.
Did you observe any major departures from this solution ? (ie do I need to update this thread to contain a new nugget of information or has the configuration requirements changed ?)
Edit: looking at your two posts the difference between the config entries escapes me. What is the difference ?
I think overall, I found it hard to understand why the error I got when I first installed the plugin says I have to enter my token, which I did but then it won’t save. I knew from other guides I had to also update the “accept_terms” and “domains”, but I most of been getting an error, but never knew.
To be honest @Mutt I really thought I had an issue with the file not being able to be written too as I tried changing many of the sections and every time it just went back to default (I know now it was just an error, just that the UI does not report that to the user). So I never knew to try to copy other configs here.
