Issue regaining external access

Configuration
1

I recently upgraded to a google wifi router and love it, however ever since doing so i’ve not been able to set up my external access as i previously had it.

Currently I am having to access my instance via https://xxx.duckdns.org:8123 which is fine up until i want to use the alexa component which i previously configured. I can’t have the port number in the alexa endpoint url so need to get my port forwarding sorted.

I have port 80 external forwarding to 80 internal already.

setting up port forwarding on the google wifi is easy through the app, but i’m not getting the results i expect.

When forwarding 443 external to 8123 internal and i access xxx.duckdns.org either inside my network out on 4G, i just get a white page with a blue bar at the top. If i add :8123 to the url whilst this port forward is active, i can see the login screen but after entering my password it says that it’s failed to connect.
I am able to access my instance via https://192.168.1.35 on my local network however, but the google wifi supports nat loopback so i should be able to use my duckdns regardless of being connected to wifi or not

any clues on what i’m missing here?

2

in my config i have this:

    http:
       server_port: 443
       ssl_certificate: /ssl/fullchain.pem
       ssl_key: /ssl/privkey.pem
       api_password: XXXXXXX
       base_url: XXXXXXX.duckdns.org:8123

and i’m actually able to access my instance externally using https://xxx.duckdns.org:8123 if i set up a port forward for 8123 external to 443 internal…which doesn’t make much sense to me

3

ok, issue sorted, not 100% sure how but had to remove
server_port: 443

from my config, forward 443 external to 8123 internal and it now works with just my duckdns url, no port needed.