Using 2 Nextcloudpi instances with reverse proxy (by NGINX Reverse Proxy Manager)

[scubamuc]

hey @Christoph_Weber and welcome to the community

@Christoph_Weber

Now I want to use another nextcloudpi instance with another dyndns service (duckdns): “domain2.duckdns.org”.

ahh that’s where your issue is. see here 101: Network, domain and DNS to get an idea of what is required

@Christoph_Weber

But when I call “domain1.ddns.net” or “domain2.duckdns.org” I cannot reach the nextcloudpi. I get the message: “Too Many Redirects” of the webside. I cleared the cache of the browser, but the error is still there.

you only have a single point of entry pointing to your reverse proxy. so you can’t have two DDNS providers pointing to your routers public IPv4 address.

suggest you do the following;

• domain1 is working and is your primary DNS acting as your single point of entry for your reverse proxy
• domain2 does not need its own DDNS, thus forward domain2 to your primary DNS on "dyndns service (no-ip) "

that way your reverse proxy will be listening for domain1 and domain2 coming from your primary DNS on "dyndns service (no-ip) " and forwarding client requests to the configured instances.

in other words, don’t use two DDNS providers, but forward your domains to your primary DDNS and let reverse proxy look at the domain names being visited and forwarding the traffic accordingly