How to configure Nginx reverse proxy for subdomains using MyFritz.net DDNS?

[buentjen]

Hi everyone,

I'm trying to set up Nginx as a reverse proxy on a home server (Docker-;Container in Raspberry Pi) located behind a Fritz!Box router. I'm using the MyFritz.net DDNS service (xxxx. myfritz. net) to access my network externally.

What Works:

Port forwarding (80/443) from the Fritz!Box to the Nginx server is configured.

Accessing services via the main MyFritz! address (https://xxxx.myfritz.net) works perfectly. Nginx correctly forwards requests to the designated backend service.

What Doesn't Work

I want to make different services accessible via subdomains (e.g., service1.xxxx.myfritz.net, service2.xxxx.myfritz.net).

When I try to access such a subdomain, the connection fails.

[Wembly1]

I stepped over the same problem.

The problem here is that myFritz doesn't resolve any sub-sub-domain yyy of yyy.xxxx.myfritz.net.
Only such sub-sub-domains are resolved for which you have created a "myFritz Sharing" within your Fritzbox. When you do so, the hostname of the target device (or name that you assigned in Fritzbox to this network device) will automatically become yyy sub-sub-domain. The problem with this is that it is impossible to have multiple yyy sub-sub-domains assigned to the same local network device. Fritzbox doesn't allow to set the name manually. So it shall be fine as long as you only want to redirect a single service via NPM. If you have multiple services on the same machine, then you could not use myFritz.

This is at least what I found out with my 7490 OS 7.60. Therefor I used ipv64.net DynDns instead.

[buentjen]

Thanks a lot for clarifying this!

That confirms the issue I ran into. It's helpful to know that myfritz. net doesn't resolve sub-sub-domains.

Since this prevents mapping multiple sub-sub-domains to the same local server, I guess I'll definitely have to use a different DynDNS service. Thanks for the insight!