Will try to be succinct, but there’s something wrong with my setup and I’d love a bit of help if at all possible.
Started with a standard duckdns setup, and that let me be able to access things outside of the network using the duckdns url but not inside it. Inside, I got a security exception that I could ignore on a desktop browser and proceed with, but not on the ios app.
…and I think my issue is I can’t pass the step 5 check where I should be able to see http://{myurl}.duckdns:8123 inside my network. I can’t, and I don’t think Caddy can either. I can see things using the local ip though.
Removed that, didn’t seem to affect things. Do you have anything in config under http:
for?:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
If they’re not there I can’t get in externally, but I can’t use the secure connection internally either way.
That won’t work… has to be https and you don’t specify a port.
Internally, use http://ip-address:8123
Also with duckdns, you don’t want to generate ssl certificates as caddy does that for you.
What you could try is removing the duckdns addon for now and manually setting your duckdns ip on the duckdns site itself just to check if it works.
You will need port 443 forwarded to 443 and port 80 forwarded to port 80. I use a different high numbered port forwarded to 443 so the 443-443 could be 20000 to 443 for example. 80-80 is needed to generate the ssl certificates. You could use the duckdns addon to do the ssl stuff for you and then reference that in the caddy file too…
If you go to duckdns.org and login you can enter the public IP address for your router there and update the setting. Actually not sure how duckdns addon sets up the duckdns account - I’ve never used that because my router handles that (or it did before I switched to using IPv6)
What is your setup? Raspberry Pi? If you’re on a Linux install I use a script and cronjob to handle the duckdns updates for me… I can share that with you if it will help. Then you don’t need to think about the duckdns addon…
I’m not sure what you mean… if you ping your domain from a command prompt, is the IP address the same as your public IP address? It seems there’s just something simple missing preventing this from working for you.