Coll abora Online under ISPconfig 3 and LAMP

Discussion in 'General' started by axxies, May 10, 2020.

  1. axxies

    axxies Member

    I am fiddling with setting up NextCloud with Col labora Online under ISPconfig3, but that has turned out to be really hard. I simply can't get it to work.

    I have already set it up under Ubuntu 18.04 on another server (without ISPconfig3) and that was super easy since the installation guide was clear (I am not much of a Linux geek, I learn what I need so I am not a total noob either, just close to :) ) and that was easy. It was under LAMP with docker.

    Now I am trying to do the same on a stretch server (LAMP) wth ISPconfig 3 and docker and I can't get collabora to work from NextCloud and under ISPconfig3. NextCloud works like a charm, but colabora doesn't. These two must be on separate domains.

    Here is the guide to make it work on a plain server without ISPconfig3,
    https://nextcloud.com/collaboraonline/

    ...but for some reason I don't get it to work under ISPconfig3 and stretch if I do what this guy did under Ubuntu 18.04 is set up according to this (maybe that works differently than under stretch):
    https://www.allerstorfer.at/install...extcloud-15-with-ispconfig-3-on-ubuntu-18-04/

    For this to work with coilabora there must be a reverse proxy and I have set that up.


    NextCloud works like a charm here too, but collabora is the problem. I prefer to run collabora on a docker instance, since I have seen at many places that collabora is really sensitive so a docker installation is to prefer.

    When I try to connect with the collabora-domain with https, it redirects to the default page of Apache. I don't know if I can get rid of the DocumentRoot completely in ISPconfig3 and this probably needs to be done since the connection should go to the docker instance instead. The interesting thing is that collab ora's admin panel (under https) works and I am able to login there:
    https://<mydomain>/loleaflet/dist/admin/admin.html

    but not to the domain only:
    https://<mydomain>/

    Anyone who has done this under ISPconfig3, Apache and Debian and got it to work?
     
    Last edited: May 10, 2020
  2. ahrasis

    ahrasis Well-Known Member

    It seems simple, though so far that I know ISPConfig does not support docker out of box, but nothing in the referred guide says that he opened https://<mydomain>/ via browser as well except he just added that in his installed nextcloud as an admin.

    Theoretically, if you managed to login via https://<mydomain>/loleaflet/dist/admin/admin.htm then should be able to access the said domain just fine too, unless, you did miss a step somewhere, so I'd say retrace you steps or check if the vhost do give you that access.
     

Share This Page