@Alvizq wrote:
Hey guys. I am a new in HA and I am trying to configure DuckDNS on mi HA with no luck.
I have 2 routers. The first, a ZTE F680, and a second, wired to the first one, a Xiaomi Mi Router 4A, with fixed IP 192.168.1.128. All my devices are connected to the Xiaomi Router, including the raspberry with a fixed IP 192.168.2.2.
I followed the step by step guide from “DuckDNS - It’s not just me, It’s you” (https://community.home-assistant.io/t/duckdns-its-not-just-me-its-you) as I thought I would fix my problem, but It didn’t.
Following the steps in the post above:
- DuckDNS correctly installed
- NGINX correctly installed
- Port Forward 443
Here I forwarded external port 443 to 192.168.1.128:443 (Xiaomi Router), and from there, to 192.168.2.2:443 (Raspberry). I am not sure if this is correct or there is a better way to do this (like DMZ?)
F680 Router:
Xiaomi Router:
- Port Forward 80: I am able to forward this port on F630 router, but I can’t in Xiaomi.
- Take note of my external IP: OK
- Go to DuckDNS, create a domain, take note of the token, etc… : OK
- Change DuckDNS Add-on config and replace “mydomain.duckdns.org” and “token”: OK
- Save and start DuckDNS. OK
Log:
- INFO: Using main config file /data/workdir/config
- Account already registered!
[12:03:51] INFO: OK
MY EXTERNAL IP
NOCHANGE- INFO: Using main config file /data/workdir/config
Processing MYDOMAIN.duckdns.org- Creating new directory /data/letsencrypt/MYDOMAIN.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 MYDOMAIN.duckdns.org
- 1 pending challenge(s)
- Deploying challenge tokens…
OK + Responding to challenge for MYDOMAIN.duckdns.org authorization…- Challenge is valid!
- Cleaning challenge tokens…
OK + Requesting certificate…- Checking certificate…
- Done!
- Creating fullchain.pem…
- Done!
- Change confing in NGINX addon, replace the domain
- Start NGINX: OK. No errors in the log, at the bottom shows “INFO: Running nginx…”
- Goto your configuration.yaml and comment out ANYTHING under http: including the “http:” itself. OK
- Reboot routers. OK
- Reboot Hass. OK
- Goto [https://mydomain.duckdns.org] and login to your HA instance.
Of course step 14 does not work at all.
Also:
- I checked my ports in www.yougetsignal.com/ and they appear to be closed (or the device not answering. It just time out)
- I cannot get samba to work either. Maybe this is all related to the same router configuration
This is all driving me crazy…
What am I missing? What am I doing wrong?Thanks!!
Posts: 7
Participants: 3