You would pass it to the address and port of the other web server that you have running Nextcloud directly. This is highly dependent upon your setup, so I can’t be more specific based on the info provided.
I’m running Ubuntu server 22.04, nginx 1.18 and NC25. nginx has been left in it’s default state except the nextcloud conf file. Well, there’s another subdomain running, also proxied, but that one works fine (Navidrome), since I can address a port. What more info should I provide? The config.php?
In this case you you don’t need a reverse proxy configuration for Nextcloud. Reverse proxy configurations are only needed, if you want to proxy (pass) the connection to another web server, which can either run on the same server (listening on another port) or on a diffrent server (listening on another IP)
That’s because Navidrome provides it’s own web server, but Nextcloud doesn’t, or at least it doesn’t, if you have installed it manually from the zip file.
I’m not very familiar with configuring multiple server blocks in nginx, because I mainly use Apache. But I’m sure you can add one sever block for Navidrome, that proxies the connection to the web server of Navidrome, and then add another server block, using a “normal” server configuration instead of a reverse proxy configuration, that serves the local folder where Nextcloud is installed.
Is Navidrome running on the same server, where Nextcloud and nginx is installed? If so, try to use localhost or 127.0.0.1 instead of the actual IP address of the server. Also you have to add the port like this…
Other than that I’m not sure, because I’m not very familiar, with neither nginx or Navidrome.
You also have to use a different subdomain for the Navidrome config, otherwise nginx cannot know which server block it should use, and will probably always try to use the first one.
Is Navidrome running on the same server, where Nextcloud and nginx is installed?
Also you have to add the port like this…
Neither of them. Like this proxy_pass http://192.168.0.25:4533;
But, I might have found the solution by simply deleting the “default server” out of Navidrome’s conf file. After I did that, unless this is a stupid idea for whatever reason, it works as expected (just had to clean my browser cookies). So thanks to your explanation I learned something important and now have a working server again. Thank you!
But now, when I had another look into Navidrome’s conf file, the default server directive is back in (but it still works). Really? Could that be? Well, but it runs, what is most important. I will try to understand, what is going on under the hood.
Not sure, because as I said, I’m not an expert on nginx.
If you want to learn how it works, I would recommend to setup a test server, maybe in a VM, install nginx on it and setup a few test sites (for a start, it can be as simple as a few “Hello world” html files). Just play around with diffrent configuartions and see how it behaves. There is also a ton of guides and how-tos about nginx out there…
Using NGINX you COULD utilize the FPM feature of NGINX, and use FPM-PHP on a different host (where you also installs Nextcloud). With that setup, you basically uses the NGINX as the webserver, and connects to the PHP server over network. This will save you a little bit of overhead, of running two webservers, where your current NGINX is used as a reverse proxy. A setup like that is good for spreading the load, and isolating resources. Example:
One frontend->several webapss.
One webapp uses a lot of resources from time to time, which in a traditional webserver setup serving several apps from the same host, shares all the same resources, and this would severely effect performance of the other apps. Instead:
One webserver serves only the HTML response, and the backend services are all running on several seperate hosts, hence one heavy loaded webapp will use the resources on the host of that app only.
Long story short: It makes sense to seperate your frontend from your backend by using NGINX as a frontend with its own reserouces, and the backends seperated with dedicated resources. NGINX supports both reverse proxy and FPM, to achieve this.