[SOLVED] ERR_CONNECTION_REFUSED when trying to access NC through internal network

[Blue-R]

The issue you are facing:
I’m getting ERR_CONNECTION_REFUSED when trying to access NC internal to my network using my domain name “https://xxxxnextcloud.mywire.org/nextcloud/”.

However, it works as intended when accessing NC outside my network.

My setup is as follows:

1. DDNS, TLS and reverse proxy is handled through pfsense.
   2 I have a piHole setup internal to my network and I have created a local DNS record pointing my domain name “https://xxxxnextcloud.mywire.org/nextcloud/” - 192.168.140.180 (NC server)
2. NC config file looks as follows:

4. tracert internal to my network looks fine (see below):

If I try to access NC internal to my network using the below url it works:
http://xxxxnextcloud.mywire.org/nextcloud/index.php/login

I’m at a lost at the moment as to why it’s not working.

[bb77]

@Blue-R

TLS and reverse proxy is handled through pfsense

In this case, the local DNS record for should point to the reverse proxy instead of directly to your Nextcloud server. See the following post in the Netgate forums on how this can be achieved in a split DNS scenario: https://forum.netgate.com/post/878680

[Blue-R]

Thanks for that. That seems to have fixed my issue.