Second Nextcloud installation on same network

ℹ️ Support
,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Latest AIO
  • Operating system and version (e.g., Ubuntu 24.04):
    • TrueNas Scale 25.04
  • Web server and version (e.g, Apache 2.4.25):
    • replace me
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Nginx
  • PHP version (e.g, 8.3):
    • replace me
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • Today
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I have Nextcloud succesfully installed on Truenas scale, as ix-application (say old style). It is accessible via cloud.mydomain.com with ssl cert via Nginx Proxy Manager proxy (which also runs on the same Truenas server, running on local IP 192.168.178.10. This is my old & current server.

I’m now in the process of creating a new server and only when everything is running properly will I migrate the actual data archive. I have Dockge installed for the docker installation, and Nginx Proxy Manager (NPM) is also up and running on this server (although nothing specified yet).

But because of the opportunity I decided to switch to Nextcloud AIO. Here I’m getting stuck at the domain specification. When using the domain I have it correctly mentions it is already in use elsewhere.

How would you advise to move forward? Take the new server down, setup NPM on the new server so that cloud.mydomain.com redirects to the new address? Or can I run them in parallel, without having to setup a new domain/cert etc?

When finished, the new server will take over the role of nextcloud instance, while the old server will purely be Truenas archive for replication jobs (remote backup). I therefore don’t need to have permanent solution.

2

Just create an other subdomain, cloud2.mydomain.com and point the DNS to the correct IP’s.
But you have to add that in the router and perhaps also to a reverse proxy.
We do that with our Synology NAS for 10+ subdomains, including multiple Nextcloud installs.

3

So just specifying the second proxy in NPM so that it connects with new internal IP?

I don’t feel like creating a new SSL certificate for the second domain (on purpose I created an SSL for cloud.mydomain.com instead of *.mydomain.com . Would it hang on that?

4

Yes. Every target has to have its own SSL cerificate, unless you use a ‘wild’ certificate.

I have no experience with NPM. But that seems to me a development environment.

Create a subdomain with your ISP to point to the IP address of the install.
At home you should redirect the call to the correct install on your local IP, in fact ‘name based’. So you should use a reverse proxy server on your local network if you have multiple sites to serve.