Nextcloud Office not able to start server

ā„¹ļø Support šŸ“„ Office
, , , , ,
1

Iā€™m running Nextcloud AIO on Debian 12 ( Nextcloud Hub 8 (29.0.3)). And everything seems to be working fine. Iā€™m am trying to get Nextcloud Office working but I keep getting the following error

"Could not establish connection to the Collabora Online server.

Failed to connect to the remote server: cURL error 28: Connection timed out after 5003 milliseconds (see libcurl - Error Codes) for https://cloud.mnarch.ca/hosting/discovery"

Iā€™ve tried to follow the debug steps (How to debug problems with Collabora and/or Talk Ā· nextcloud/all-in-one Ā· Discussion #1358 Ā· GitHub) and I donā€™t see anything about WOPI at all.

AIO Office
AIO Office1902Ɨ879 166 KB

I then go into the container and run ā€˜curl -vvv https://$NC_DOMAIN:443/hosting/discoveryā€™

And get the following:

  • Host cloud.mnarch.ca:443 was resolved.
  • IPv6: (none)
  • IPv4: 142.134.158.213
  • Trying 142.134.158.213:443ā€¦
  • connect to 142.134.158.213 port 443 from 172.19.0.8 port 39944 failed: Operation timed out
  • Failed to connect to cloud.mnarch.ca port 443 after 130515 ms: Couldnā€™t connect to server
  • Closing connection
    curl: (28) Failed to connect to cloud.mnarch.ca port 443 after 130515 ms: Couldnā€™t connect to server
    exit

I have DNSmasq running and have my hosts file pointing cloud.mnarch.ca to my server.

Not sure what else Iā€™m missing.

Any help would be greatly appreciated.

Robert

2

This is your issue. Most likely does your router not support NAT loopback. You can work around this by following GitHub - nextcloud/all-in-one: šŸ“¦ The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

3

So Iā€™ve followed https://www.howtogeek.com/devops/how-to-run-your-own-dns-server-on-your-local-network/ and this is my hosts file:

127.0.0.1 localhost
127.0.1.1 MNACloud.cloud.mnarch.ca MNACloud
192.168.0.4 cloud.mnarch.ca
The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Am I missing something still?

4

Iā€™m not sure if pointing the public fqdn to the local host works in your setupā€¦ but seems it doenā€™t work either:

if your hosts file would work the connection would go to 192.168.0.4ā€¦ Maybe Probably DNS help with NC Docker + Collabora + Wireguard tunnel - #5 by wwe helpsā€¦ If I donā€™t miss anything important I think in case of aio you have to add the alias to the apache container

5

So I solved the issue. I needed to get a valid certificate by inputting 'my.domain.com:8443" after that everything was good to go.