Hi

Very new to all this. I'm trying to setup NextCloud with Nginx Proxy Manager on Truenas Scale according to this (https://forums.truenas.com/t/a-full-guide-for-installing-nextcloud-on-truenas-scale-with-collabora-integration-and-outside-access-through-nginx-proxy-manager/5874)

NPM is returning an internal error when I try to configure the proxy.

Appreciate any points. Thanks

Can't edit my post, so will reply instead:

- tried to create a SSL certificate and test connectivity. NPM returned that a server was detected but returned an unexpected status code "invalid domain or IP". I'm using a domain provided by my router, and have already setup port forwarding for ports 30022 and 443 to the server running NPM.
- pinging my domain returns the public ip. however if i telnet my domain via 443, the connection fails. there's no firewall/router setting that blocks this (and connection has worked under other installation attempts), so don't understand why this is despite the port forwarding



Edited 1 time(s). Last edit at 09/21/2024 10:34PM by PZ0013.

- telnetting my public ip on port 443 also results in a failed connection

So testing across different NPM installations:

When NPM is installed as a TrueNAS app:

- when trying to create a certificate, server reachability is failed. The error is that a server can found but returned an unexpected status code ‘invalid domain or IP’
- port 443 and 30022 (as required for the app) has been forwarded to the device running NPM, however I’m not sure if the port forward is actually running properly
- check with www.portchecktool.com shows port 443 is blocked, but port 30022 is ok

So to check this isn’t an error with my router settings, I also tried NPM installation in a Docker container:

- same error when creating a certificate as above
- port 443 has been forwarded to the device/container running NPM. (port 30022 not required with the Docker installation)
- this time with the portchecktool, port 443 is shown to be clear

So in:

1) the TrueNAS App installation, the App somehow blocks/is not listening for traffic on port 443; and
2) the Docker installation, port 443 is cleared but NPM can’t process the certificate? Would anyone be able to make sense of this?