Some trickery needs to be employed for the name to function correctly. Physically the connection is routed from the internet to my ip address through my router (which port forwards 80/443) to the Apache Web Server/Reverse Proxy. In my instance and either have to have an “A” or “CNAME” entry registered. I’m also using Cloudflare as my DNS provider (highly recommend – its free and totally gives you control of your Domain Names). (Other domains are contained within the certificate which describe other Virtual Hosts running within the Apache FreeBSD installation). I don’t believe you need fully qualified domain names when running things over simple http. Collabora/Docker in this scenario doesn’t have a FQDN – its just known as 127.0.0.1:9980. (this is used for the Apache Reverse Proxy Virtual Host that then proxies unencryped requests towards Collabora/Collabora Docker) (this will be used for the NextCloud Virtual Host – as named in apache) The FQDN’s are necessary for SSL to function – but it also complicates things since when setting up things you need to refer to each individual server by FQDN and not by IP address. Both the the Apache Reverse Proxy (FreeBSD) and Apache Reverse Proxy (Ubnt) have a Fully Qualified Domain Name (FDQN) that is contained within the Lets Encrypt SSL certificate. Nextcloud runs as virtual host on FreeBSD ApacheĬollabora/Docker runs on the Apache Reverse Proxy (Ubnt) Internet -> pfSense Router -> Apache Reverse Proxy (FreeBSD) -> Apache Reverse Proxy(Ubnt) I unfortunately have two Reverse Proxies in my setup (I suppose many of you may have one – this complicated setup unfortunately was needed because I can’t run Docker containers within freebsd (or at least it doesn’t work well)) I’m using the Collabora Docker image and not the server installation.
Nextcloud is located on a different machine than collabora.Ĭollabora is installed within an Ubuntu 18.04 VM within FreeNAS. Nextcloud is installed within a freebsd jail (I used these instructions: ). My setup (which may be different than yours).įirst I’ve virtualized my entire setup running within FreeNAS. This is a straight Collabora Docker installation I’m NOT running Collabora Code or the combination product that contains the docker image of Nextcloud/Collabora together. I know this is unusual – but I actually wanted to post a working configuration for using the Collabora Docker image.
0 kommentar(er)
