DuckDNS not working remote access

Hello
I installed Hass.io on Raspberry pi3.
Installed addons “configurator”, “samba”, “ssh” and “duckdns”.

I made the settings duckdns as described in https://www.juanmtech.com/hassio-duckdns-add-on-set-up/
Now if I log in from the local address (192.168.1.xxx) in the home assistant connection has become protected (https).
If I try to connect from the external network at the address https:\mydomain.duckdns.org:8123 then I get the message “ERR_CONNECTION_TIMED_OUT”
Raspberry pi connected as follows:
rpi3(192.168.1.20)(192.168.1.1)router1(192.168.0.5)(192.168.0.1)router2(10.xx.xx.xx) to provider. IP adress provider - not static.
In router1 i make 3 rules port forwarding:
1.interface ISP, protocol TCP port 80 to 192.168.1.20 port 80
2.interface ISP, protocol TCP port 443 to 192.168.1.20 port 8123
3.interface ISP, protocol TCP port 3128 to 192.168.1.20 port 3128
I did not get access from the external network.

Then I also tried to write similar rules for router 2:
1.interface ISP, protocol TCP port 80 to 192.168.0.5 port 80
2.interface ISP, protocol TCP port 443 to 192.168.0.5 port 8123
3.interface ISP, protocol TCP port 3128 to 192.168.0.5 port 3128

It also did not lead to success.
Please Help me set up remote access.

P.S. After installing the duckdns and setting ssl to “true” addon “configurator” opens only in panel “addon” through " open web ui" Is this correct?

Did you add base URL to your configuration.yaml?

Hi, I am having similar problems in trying to use nginx. I followed carefully the notes to set up the addons. I am now convinced the issue lies with either my router not forwarding correctly or my ISP using GCNAT. Please leave a message if you solve the issue and I’ll do likewise.

Yes.In configuration.yaml:
http:
base_url: mydomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

Try connecting to your url without adding the port

If your ISP side of that router is really 10.x then you are on a carrier grade Nat. You can’t forward anything.

I have it with the https: in front:

http:
  base_url: https://mydomain.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

I tried http, https, with and without a port number.
No connection :frowning:

I am not an expert on networking. Mi-home somehow works when externally accessed…

question? I dont use hassio hence the question.
how are you getting your ssl certificates?
did you install the letsencrypt add-on?

I understand when install the addon duckdns automatical installed letsenkrypt. So after installing the duckdns was made possible entrance into the home assistant from the local network by https.
Also certificates fullchain.pem and privkey.pem appeared in the catalog \ssl

Did you forward ports to get that to work? A lot of services will have a way to connect out to the cloud and creates a way back in without port forwarding.

Do I still need to set ‘base_url’ in 2022?
The official doc doesn’t mention anything about base_url