![]() I am not able to reach the Collabora server via web browser from either outside or inside my home network. Anyway, while you may activate the desired solution and its integrated Document Server in the Apps-section of Nextcloud, my preferred choice always was to use a. It is also set to forward 80 to the internal IP for my Collabora server. My router is set to forward 80 and 443 to the internal IP for my NC server. They’re easy to deploy and manage with Juju.Juju makes it practical to host a personal cloud. The Collabora Online plugin allows for online collaborative document editing within the Nextcloud. I use NoIP to link my home IP to my domain name for the NC server ( abc.net) and have the subdomain of setup to also forward to my home IP. Nextcloud provides file hosting and several collaboration tools, like contacts, calendars and task boards. Once setup, I switched 80 and 443 back to the NC server and am using 80 on the Collabora server. Since the NC server uses port 80 and 443, I had to turn off the port forwarding on for my NC server and use port 80 on the Collabora server for the initial SSL setup. My NC server is on a RP3b+ running Ubuntu and is also setup with letsencrypt. I used the instructions here to install Collabora CODE and the instructions here to setup reverse proxy for Apache2 with SSL using letsencrypt. Collabora server is Intel 64bit running Ubuntu 18.04, Apache2 version 2.4.29 (Ubuntu), Collabora CODE 4.2.2 (linux 圆4 version).
0 Comments
Leave a Reply. |