- NEXTCLOUD COLLABORA CODE REFUSED TO CONNECT INSTALL
- NEXTCLOUD COLLABORA CODE REFUSED TO CONNECT DOWNLOAD
NEXTCLOUD COLLABORA CODE REFUSED TO CONNECT INSTALL
You can use the OCC command line tool to install the built-in server: sudo -u Where wwwrun is the user of your web server.
NEXTCLOUD COLLABORA CODE REFUSED TO CONNECT DOWNLOAD
The internal ip without a valid cert? Wondering for my home lab setup that has the same nginx reverse proxy in front of both services. The download is rather big so it is possible you experience a time-out when using the web interface.
Searching around, I found it could be related to the docker container not resolving the ip address properly, in this case it needing to be the internal ip. Searching around, I found it could be related to the docker container not resolving the ip address properly, in this case it needing to be the internal said in Collabora CODE and NextCloud Integration Shows Blank Editing Page and Spinning Circle: Wsd-00026-00053 17:36:11.048893 ERR Failed to add session to with URI : Connection refused| wsd/DocumentBroker.cpp:1041 Error: Connection refused| wsd/Storage.cpp:446
Getting the following logs from the docker container: wsd-00026-00053 17:36:11.045672 ERR Cannot get file info from WOPI storage uri. So we are close, but no cigar.Īny idea where to look or where to start? But on NextCloud, we just get a spinning wheel and the screen stays blank otherwise. The Collabora console lists the file being opened. When we go to open a document in NextCloud, it clearly connects to Collabora now and starts to open the document. After doing this, things started to almost work. We had to add a hosts file entry for the Collabora server to NextCloud so that it would know to point to the reverse proxy internally. It gives a "saves with with error" and says to use the same protocol, but we are, so that is confusing. We added the Collabora App, and entered the external name of the Collabora server. NextCloud has been in production for a long time, no issues there. We can bring up the admin console and see the status of the system over HTTPS. Collabora is up and running and can be accessed from the outside through the reverse proxy. we have an NGinx Reverse Proxy, but this sits on its own server in front of both of the other workloads.
What we are doing is a little more advanced than any guide we've found, so we suspect that the issue is from that. Trying to get NextCloud and Collabora CODE working.
0 kommentar(er)
