I have one problem…I can access remotely and from my PC, but not from my phone when I am connected to my LAN
So your router does not allow loopback… this is your router, not duckdns.
i think thhe same, the only problem is that i cant access throw my phone when i am connected to my LAN … if yu could help me please
either get a router that allows loopback or use the local ip address
1 Like
thanks i allready fix it, it was my phone, i change the DNS1 to my rp3 address
this is a nightmare…
I get the certificates DONE with port 80 to 80 , 443 to 443, 8123 to 8123 after this I change the yaml
like this:
base_url: “https://xxx.duckdns.org”
ssl_certificate: “/ssl/fullchain.pem”
ssl_key: “/ssl/privkey.pem”
api_password: xxx
save and change the ports like 80 to 8123, 443 to 8123 and 8123 to 8123
reset hassio and never can access to frontend, internal ip nothing duckdns url nothing
I haven`t api_password with the new authoritation after 77.2 but if I remove it still the same
could you help please
You can check the certificates are DONE but I can`t access via internal ip orduckdns
INFO: Using main config file /data/workdir/config
- Generating account key…
- Registering account key with ACME server…
- Done!
Tue Sep 25 20:20:46 CEST 2018: OK
xxx.xxx.xxx.xx
NOCHANGE
INFO: Using main config file /data/workdir/config
- Creating chain cache directory /data/workdir/chains
Processing xxxx.duckdns.org - Creating new directory /data/letsencrypt/xxxx.duckdns.org …
- Signing domains…
- Generating private key…
- Generating signing request…
- Requesting new certificate order from CA…
- Received 1 authorizations URLs from the CA
- Handling authorization for xxxxxx.duckdns.org
- 1 pending challenge(s)
- Deploying challenge tokens…
OK + Responding to challenge for xxxxx.duckdns.org authorization… - Challenge is valid!
- Cleaning challenge tokens…
OK + Requesting certificate… - Checking certificate…
- Done!
- Creating fullchain.pem…
- Done!
I’ve got the ports 8123, 443 and 80 forwarded to themselves, re-installed DuckDNS add-on but can’t get the certificates to be created. I only get “KO” with the timestamp. Nothing else.
I followed this guide but kept getting errors both in Config and DuckDNS startup. So, I tried the advice above to uninstall the add-on and change port forwarding until the certificates are created.
Any help is appreciated.
Thank you
BTW, BRUH video uses Putty but some guides do not. Which way is correct?
BTW, Found my port 80 and 443 is not visible from outside. 8123 is open. Checked with Comcast. Open on their end. Have all the ports correctly forwarded on the router page!!! Frustrating
Hi there and welcome to my world!
Having the same said issues. Have you set up the port forwarding on your router?
Have a look at this, good tutorial:
I’ve managed (I think) the port forwarding side of it but haven’t yet got a fixed IP address set up, struggling with that at the mo.
Please let me know if the video helps
Thanks
You solved my issue:)
This has been a problem for several months
xx_Nexus_xx spent weeks on this on and off , followed this to the letter (uninstalling all that could conflict) then proceeded. I have full HTTPS ! - thank you.