Hello,
I have a problem with TrueNAS-SCALE-24.10.2, nginx proxy manager and nextcloud. I have been trying to get nextcloud to run reliably for weeks now. Since it only works locally with Apple devices I decided to address it via NPM.
I installed Nextcloud and NPM on a test system with 25.04-RC.1 (192.168.178.167). I set up DynDNS and installed port forwarding to NPM on my Fritz! Next2.mydomain.com is forwarded correctly to 192.168.178.167:30027 (with wildcard-SSL to *.mydomain.com).
In the next step, I installed the whole thing on my target system (192.168.178.6) with 24.10.2. Port 80 and 443 on the Fritz!Box are forwarded to the NPM. I also set up the forwarding to Next2.mydomain.com 192.168.178.167:30027. Works. However, when I now set up Nextcloud on the target system with the same settings (except for domain name and IP), I always get an error because Safari cannot connect to next.mydomain.com.
NSlookup returns the correct external IP address for both systems
next.mydomain.com and next2.mydomain.com.
What is going on here? Where is my error? Should I reinstall Nextcloud?
On the 24.10 system, Is NPM listening on the 80-443 ports, instead of the TN webgui?
I have a port forwarding on my router to the NPM:
80 → 192.168.178.7:30021
443 → 192.168.178.7:30022
And it works for my test system. It is forwarding correct to the gui of
nextcloud - next2.mydomain.com (192.168.178.167:30027)
truenas - truenas-test.mydomain.com (192.168.178.167:443)
but not to
truenas22.mydomain.com (192.168.178.7:443)
next.mydomain.com (192.168.178.7:30027)
So NPM is working, but 192.168.178.7 does not reply correct.
truenas22 is listening on 192.168.178.6 and 192.168.178.7. Could this be a problem?
when I try to open truenas22.mydomain.com I see:
when I remove the second IP address on my primary truenas system (192.168.178.6) then I can’t reach my test-system?
It shows for a short time next2.mycloud.com in the browser address bar then it switches back to 192.168.178.6 ???