Duck Dns with Nignix Proxy eero secure error

Configuration
1

hello developers I have a problem with duck dns I have installed duck dns and nignix proxy and add and modified configuration by putting correct domains and token so my duck dns logs are very correct and working so good same goes to nignix proxy I have put domain in configuration of nignix and copy the proxy of nignix and paste it to configuration.yaml in file editor so everything is fine now when I setup my router setting to port forwarding I used external port 443 to internal 8123 and saved it but whenever I write my domain name.duckdns.org it give me eero secure error.

Screenshot 2022-07-21 131303
Screenshot 2022-07-21 131303841×504 25.1 KB

please help me I am worried.

2

Are you using Nginx Proxy Manager? Because then you shouldn’t forward to port 8123 in your router, but to 443. And set up the proxy to forward to your HA machine at port 8123

3

Thank you for your reply I am using this nignix proxy app

2
2952×478 48.8 KB

or what should I do? in my port forwarding?
3
3717×121 14.7 KB

4

I found this post on the forum which seems to explain all the details:

5

And yes you should port forward 443 to 443 and 80 to 80 (if you haven’t changed the default ports in the NGINX addon)

6

so sir nothing can change here it is correct?

5
5993×300 22.4 KB

7

You can change it if you want, but you will need to redirect to that port

8

by going to port forwarding and rewrite the internal or external = 443?

9

if you don’t change the port in the addon. You should redirect external port 443 to internal port 443 in your router

10

okay so

6
6963×303 17.3 KB

I did this setting to nignix network port as mentioned in the support link you have sent so can you guide me little more now what I have to change in port forwarding in the router what is my internal or external port now?

11

so eero secure error is remove while configuring the port forwarding to 18123 to 18123 but whenever I write the url https://name.duckdns.org:18123/ it is now give me site can’t be reached error.

12

like it is going very well like in the reference you sent but in the end it give me refused network error.

13

Do the logs of the addon show any errors?