Can't connect to Nextcloud on LAN

Question

Can't connect to Nextcloud on LAN

Closed this issue 3 years ago · 9 comments

Hello and thank you @danb35 for this script 😄

I managed to install Nextcloud on my TrueNAS and configure it with my OVH domain name.
Just after the installation I logged in as admin, created users, etc.

But this morning, I can't connect to Nextcloud with my domain : cloud.ricoche.fr
I encounter an error of this type: ERR_CONNECTION_RESET
I am thinking of a configuration error or a failed step between my router (Livebox Play) and OVH Zone DNS.

I can't connect with the jail IP too.

How to find the source of the problem ?
Thank's

Answer 1 · 2022-01-11T15:28:33.000Z

Caddy logfile : https://pastebin.com/25Kbaz27
Replaced my email with xxxx

"No valid IP addresses found for cloud.mydomain.fr"
[cloud.mydomain.fr] Obtain: [cloud.mydomain.fr] solving challenges: cloud.mydomain.fr: no solvers available for remaining challenges

I don't know why it worked first, but not anymore...

Answer 2 · 2022-01-11T16:00:45.000Z

"No valid IP addresses found for cloud.ricoche.fr"

That pretty well is your problem--you need to set up a DNS record for cloud.richoche.fr pointing to your public IP address.

Answer 3 · 2022-01-11T16:13:51.000Z

Mmh ok, I created a no-ip account with this address: ricoche.zapto.org
This address has for IP / Target the IPv4 WAN address of my router : 86.198.163.189

Im my router, configured DynDns with no-ip :
Added ricoche.zapto.org, username and password.

In OVH I changed cloud.ricoche.fr to the domain (CNAME) ricoche.zapto.org
Is it correct ?

Answer 4 · 2022-01-11T22:15:15.000Z

Is it correct ?

Seems like it. Your hostname resolves to an IP address now, and I'm able to reach the login page of your Nextcloud installation there.

Answer 5 · 2022-01-11T22:20:50.000Z

Yes thank you ! In fact I can't access to Nextcloud on my local network LAN.
However the domain and the IP address are well configured :

'trusted_domains' =>
  array (
    0 => 'localhost',
    1 => 'cloud.mydomain.fr',
    2 => '192.168.1.100',
  ),

Answer 6 · 2022-02-02T11:05:27.000Z

Problem solved using a VPN when I'm on LAN, not ideal but it works well.

Answer 7 · 2022-02-02T11:07:56.000Z

I guess that's one way to do it. But what you really need to do is what I say in the README: configure your LAN (specifically, your router or whatever provides DNS to your LAN) in such a way that cloud.mydomain.fr resolves to 192.168.1.100 from within your LAN.

Answer 8 · 2022-02-02T11:12:01.000Z

Impossible because my router does not support hairpinning...
I ordered a new one which will solve this problem, I hope.

Answer 9 · 2022-02-02T13:40:15.000Z

This has nothing to do with hairpinning (although that would me another may to make this work); it's all a matter of DNS. If your router doesn't support split DNS, a local Pi-Hole instance (which runs fine in a VM on Free/TrueNAS) would do the job.