Replies: 30 comments 82 replies
This comment has been hidden.
This comment has been hidden.
-
Thank's !! That's helped me a lot, just adding the 0.0.0.0.... |
Beta Was this translation helpful? Give feedback.
-
Is there a way to do this securely ? removing all wopi adresses (same as adding 0.0.0.0/0) works for me but I would rather use a safe way to do thatand not just accept all adresses. |
Beta Was this translation helpful? Give feedback.
-
Did Adding " ,0.0.0.0/0" and solve the problem. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
Hi, I just added a few hints how to get the needed ip-address in an easier way. |
Beta Was this translation helpful? Give feedback.
-
``When I copy in bulk the logging message I get: {"....,"time":"2023-01-13T19:38:14+00:00","remoteAddr":"162.158.233.105","user":"....}. and using those steps:
I get
|
Beta Was this translation helpful? Give feedback.
-
Whenever I try to do the former method of checking the logs, I get wildly different IPs every time I try to do this, all of which correlate with Cloudflare's IP ranges. And when I try the method involving using bash inside the docker container, I get an IP that remains consistent, but is one that also doesn't work when put into the WOPI field. Unless I'm misunderstanding and I'm supposed to put like, IPADDRESS/16 or something like the other addresses have. For context, my home server is setup like this: |
Beta Was this translation helpful? Give feedback.
-
I am having a weird issue with the Talk High-performance backend in my AIO installation. The standard link which is inserted (and I guess is supposed to direct to an internal signaling server) doesn't work and it stops the whole Talk app from being able to send and receive messages. I have a valid SSL certificate and opened the ports 3478 TCP+UDP The simplest solution for me would be to stop the link from appearing again after each backup, but I don't know how to do that... The above mentioned curl command returns this log which looks like it can actually communicate with the server?!
|
Beta Was this translation helpful? Give feedback.
-
Leaving this here in case it saves someone time. I was having trouble getting docker nexctloud aio with nginx reverse proxy working with collabora. Using the steps above I realized Checking I went to https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md and compared to my nginx site config, and realized I had left a few things out. NC had been working fine for months but I had not tried collabora so had not noticed. I had left out http2 in the initial
Oh, and I suspect the main error was having left out which probably made nc try to connect to collaborate through the public ip. So- another duh- read the docs! error. Thanks again, @szaimen! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I am facing issue with nexcloud Talk. UI is showing following error The logs show following:
The issue started happening after 4.4.1 update. I am on the 4.5.0 now but the issue persists.
And got following:
I am getting the response when trying from the browser.
|
Beta Was this translation helpful? Give feedback.
-
Hi,
The reverse proxy has a Lets Encrypt certificate via certbot in place. /etc/hosts file on the host does not contain the NC-domain. I may be stupid but i don't see the input field Not sure what the next step is so any help would be appreciated! :) Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
Hi, I am struggling with talk. I am using Nginx proxy manager for reverse proxy. It was previosuly on a different host. I added trusted hosts by editing config.php. Did not solve. Is there something I can do? Thank you! bash-5.1# curl -vvv https://$NC_DOMAIN:443/standalone-signaling/api/v1/welcome
|
Beta Was this translation helpful? Give feedback.
-
I added my public IP to the WOPPI (as cloudflare zero trust tunnel hides it) Here is my output for Talk
|
Beta Was this translation helpful? Give feedback.
-
Hi, `[spreed] Fatal: RuntimeException: There can only be one Talk backend at <>
at 2023-03-20T21:41:03+00:00` Could you help me to have it working? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Regardless of what I put into Nextcloud Office WOPI allow list (docker network ip/24, localhost, ip of host on which the docker runs, reverse proxy ip) it only works when it's empty. Could someone please tell me like I'm five years old: If I leave it empty, and both collabora server and nextcloud are only accessible from internet only thru https via nginx reverse proxy (9980 port is not accessible outside of local lan) are you telling me that any user with nextcloud login can still d/l w/e they want via the WOPI thing? If so, Jesus Christ on a crutch - what do I put there? |
Beta Was this translation helpful? Give feedback.
-
I cannot find a way to whitelist wopi client in the UI I am also getting the Collabora Online should use the same protocol as the server installation. no matter what I input. any idea? |
Beta Was this translation helpful? Give feedback.
-
try using the network host mode, and open the port in your firewall. |
Beta Was this translation helpful? Give feedback.
-
Nextcloud AIO on CentOS with nginx proxy. I get blank screen when try to open .odt file. On https://mynextcloud.domain/settings/admin/richdocuments - green mark /etc/hosts Nginx conf
Collabora log from AIO interface
curl -vvv https://$NC_DOMAIN:443/hosting/discovery
UPD: I used nginx conf from documentation and it's work. |
Beta Was this translation helpful? Give feedback.
-
I followed the instructions and they (temporarily) solved my problem. The IP that was logged was the public IP of my router. So the next time my ISP assigns a new IP to me, I will have to redo this and not forget to delete the old IP. I'm sure this is not intended and I could imagine this is caused by some misconfiguration of my setup. Where could I start looking? Maybe it's related to my reverse proxy? I'm using Nginx Proxy Manager and |
Beta Was this translation helpful? Give feedback.
-
Hello, I have this error in my collabora container: |
Beta Was this translation helpful? Give feedback.
-
I have the same problem from time to time that I can't edit documents with Collabora. I'm using DynDNS. My IP address changes frequently. The IP shown in the log message is my current public IP address, so I guess I will always run into the same problem again whenever my public IP address changes. This is unfortunate and I guess also a security issue when I just keep adding a new IP address every few days. Can I somehow tell Nextloud/Collabora to automatically update that list with my current public IP and remove the old one? Or is there some other workaround for this? |
Beta Was this translation helpful? Give feedback.
-
@szaimen Hi, when I do curl -vvv https://$NC_DOMAIN:443/hosting/discovery, I get the message, "Failed to connect to mydomain.com port 443..." but, Nextcloud is working fine, portchecker.io says the port is open, and I can ping the server by domain name from inside the container. |
Beta Was this translation helpful? Give feedback.
-
Having Collabora issues (I'm newer to this, sorry if my formatting is strange or my explanations are strange) I'm having intermittent Office issues where my documents won't load for editing (mostly won't work but occasionally it decides to be kind). curl result:
$ ` Excerpt from Collabora Logs:
Thanks for the help in advance! |
Beta Was this translation helpful? Give feedback.
-
This was indeed the case, but removing it did not solve the connectivity issues I had with Collabora.
Following this instruction then solved the problem. |
Beta Was this translation helpful? Give feedback.
-
Talk issue
Log
|
Beta Was this translation helpful? Give feedback.
-
After latest upgrading a few days ago, I got the problem with Collabora, and docker said Talk and Apache are 'unhealty', and all the containers cannot access the host server from theirs command line. Try resolving DN with successful to all DN in the world except 2 DNs of my router and my nextcloud (same IP address). The basic functions of nextcloud (Files, Folders, and even Deck app) are running properly. Only the Collabora (Nextcloud Office) server is unable to connect. I have not tried Talk yet, but last week it worked fine (when Collabora also worked fine). They all works for a year. But after the latest update (by nightly automatic restart), I cannot open office documents anymore. My AIO instance is behind reverse proxy. I have migrated from one machine (Windows 10) to the new machine (Ubuntu 22.04) last month. Everything works find until a few days ago that I find Collabora does not work. I have just started searching the internet and find that it could be about the DN resolution in containers. The host machine is behind router with DDNS. I configure virtual server in the router to map port 443 to the machine. I tried 'curl -vvv https://my-domain-normally-used/' inside the mastercontainer, nextcloud, collabora, talk, and apache containers and got the same result; "curl: (6) Could not resolve host: my-domain-normally-used". I tried other normal DN such as google, bing, nextcloud and our other server names hosted on public internet. They all work. I tried the instructions at #2065, but after restart the mastercontainer, the network "nextcloud-aio" is back. All containers are still unable to resolve the main server domain name, while the other domain names are resolvable. I tried curl and dig, in containers and in the host command line.
Where should I try finding the cause of problem? |
Beta Was this translation helpful? Give feedback.
-
Sometimes, Collabora and/or Talk do not work as expected. Here is how to troubleshoot this.
A general step on Linux would first be to check if e.g.
127.0.0.1 yourdomain.com
or e.g.127.0.1.1 yourdomain.com
was added to the/etc/hosts
file on your host runnig the docker daemon. If that is the case, Remove it from the file and restart AIO which might already make things work.If you are on Synology, check if seccomp needs to be disabled: https://github.com/nextcloud/all-in-one#how-to-disable-collaboras-seccomp-feature
If you are behind cloudflare, see https://github.com/nextcloud/all-in-one#notes-on-cloudflare-proxytunnel (there are hints regarding Nextcloud Office and Nextcloud Talk)
If AIO is behind a reverse proxy, make sure that websocket are enabled in your reverse proxy config.
Afterwards, while the containers are running, do the following:
Collabora (Nextcloud Office)
First, visit
https://yourdomain.com/settings/admin/richdocuments
and if you see theAllow list for WOPI requests
input field (If you dont see the field, just skip this step), add,0.0.0.0/0
to it. This might already resolve you connection issue. However it is not secure as you allow all ip-addresses to connect by doing so.If this makes it work, you will next need to find out the ip-address that is needed here and put it additionally into the wopi-allowlist instead of 0.0.0.0/0. One way to find the correct one out is to remove the 0.0.0.0/0 from the list again, setting the loglevel to 1 with
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set loglevel --value=1
and try to open a collabora document. Then it should log the ip-address that was used inhttps://yourdomain.com/settings/admin/logging
and you can simply add this ip-address to the wopi-allowlist instead of 0.0.0.0/0. Now you can reset the loglevel withsudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set loglevel --value=2
If the steps above do not make it work, see the debugging steps below:
Run the following commands on your server:
When this is done, Please post the output into your thread and also post all collabora container logs in your thread in order to help you further
Nextcloud Talk
When this is done, Please post the output into your thread and also post all talk container logs in your thread in order to help you further
Beta Was this translation helpful? Give feedback.
All reactions