High-performance backend and Collabora Online-server are not working

ℹ️ Support 💬 Talk (spreed)
, , ,
1

Prixmox VE is installed on Hetzner’s dedicated server. Ubuntu 23.04 lxc container is installed and Nextcloud AIO is deployed on it.
Problem: TALK does not work and Could not establish connection to the Collabora Online server.

/etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

— BEGIN PVE —

127.0.1.1 nc

— END PVE —

1

2
2821Ă—203 10.2 KB

2

Hi, can you follow How to debug problems with Collabora and/or Talk · nextcloud/all-in-one · Discussion #1358 · GitHub?

3

Collabora (Nextcloud Office)

  • processing: x:443/hosting/discovery
  • Trying x:443…
  • connect to x port 443 failed: Connection refused
  • Failed to connect to x port 443 after 5 ms: Couldn’t connect to server
  • Closing connection
    curl: (7) Failed to connect to x port 443 after 5 ms: Couldn’t connect to server

Nextcloud Talk

  • processing: x:443/standalone-signaling/api/v1/welcome
  • Trying x:443…
  • connect to x port 443 failed: Connection refused
  • Failed to connect to x port 443 after 1 ms: Couldn’t connect to server
  • Closing connection
    curl: (7) Failed to connect to x port 443 after 1 ms: Couldn’t connect to server
    exit
4

Looks like you found your problem then. Your domain is not reachable from within the containers which needs to work and is likely caused by your networking infrastructure.

5

What could it be?
vm is connected via vm mikrotik,
open ports:
tcp: 80,443,3478,8443
udp: 443,3478

connected directly to the Internet - it works.
And I am connecting through the vm mikrotik does not work

6

Hey @sanchshevchuk , i had exactly the same problem, i got it to work with editing the hosts file from my docker host

i added
“IP_ADRESS FROM REVERSE PROXY” nextcloud.domain.tld

After that it worked, my guess is that the reverse proxy refuses to listen if the remote ip is the wan ip or something like that