Collabora on the same subdomain

ℹ️ Support 📄 Collabora
1

Hello,

i have an Odroid C2 at home. With the Dyn-DNS Adress “cloud.domain.tld” i get an connection to the server.
i try to install docker on the same Subdomain as the Cloud.

is this possible?

Here my Setup for the Apache:

<IfModule mod_ssl.c>
<VirtualHost *:443>
 DocumentRoot "/var/www/nextcloud"
 ServerName cloud.domain.tld

 ErrorLog ${APACHE_LOG_DIR}/error.log
 CustomLog ${APACHE_LOG_DIR}/access.log combined

<Directory /var/www/nextcloud/>
 Options +FollowSymlinks
 AllowOverride All

 <IfModule mod_dav.c>
 Dav off
 </IfModule>

 SetEnv HOME /var/www/nextcloud
 SetEnv HTTP_HOME /var/www/nextcloud
 Satisfy Any

</Directory>

SSLCertificateFile /etc/letsencrypt/live/cloud.domain.tld/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/cloud.domain.tld/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLProtocol             all -SSLv2 -SSLv3
			SSLCipherSuite ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
			SSLHonorCipherOrder     on

			# Encoded slashes need to be allowed
			AllowEncodedSlashes NoDecode

			# Container uses a unique non-signed certificate
			SSLProxyEngine On
			SSLProxyVerify None
			SSLProxyCheckPeerCN Off
			SSLProxyCheckPeerName Off

			# keep the host
			ProxyPreserveHost On

			# static html, js, images, etc. served from loolwsd
			# loleaflet is the client part of LibreOffice Online
			ProxyPass           /loleaflet https://127.0.0.1:9980/loleaflet retry=0
			ProxyPassReverse    /loleaflet https://127.0.0.1:9980/loleaflet

			# WOPI discovery URL
			ProxyPass           /hosting/discovery https://127.0.0.1:9980/hosting/discovery retry=0
			ProxyPassReverse    /hosting/discovery https://127.0.0.1:9980/hosting/discovery

			# Main websocket
			ProxyPassMatch "/lool/(.*)/ws$" wss://127.0.0.1:9980/lool/$1/ws nocanon

			# Admin Console websocket
			ProxyPass   /lool/adminws wss://127.0.0.1:9980/lool/adminws

			# Download as, Fullscreen presentation and Image upload operations
			ProxyPass           /lool https://127.0.0.1:9980/lool
			ProxyPassReverse    /lool https://127.0.0.1:9980/lool
</VirtualHost>
 <IfModule mod_headers.c>
      Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
    </IfModule>
</IfModule>

and the Apache2 error log file:

[Thu Sep 07 10:12:38.468826 2017] [proxy_http:error] [pid 21874] (103)Software caused connection abort: [client 151.252.222.237:43302] AH01102: error reading status line from remote server 127.0.0.1:9980
[Thu Sep 07 10:12:38.468956 2017] [proxy:error] [pid 21874] [client 151.252.222.237:43302] AH00898: Error reading from remote server returned by /hosting/discovery
2

why not.
just create another virtual-host-object

3

Sure but https://cloud.domain.tld/collabora won’t work.

4

But https://collabora.domain.tld will

5

Sure. But my Dyndns address is https://cloud.larsmueller.net and I can set only one domain in my Fritzbox

6

Ah… now we come closer.
I had a similar limitation. With ddns-client (https://wiki.ubuntuusers.de/DDNS-Clients/) I found out, that this limitation was ownly in my head.

Who sayed that dyndns must be handeled by your router? :wink:

7

i have no static IP Adress :frowning:

8

Me neither. With a ddclient it is possible to answer on more than one dyndns request.
I thought my rpi to forward my IP to 6 dyndns hosts

You should try this!

9

i try this at this moment. http://www.georg-keller.eu/nc/neuigkeiten-blog/news-archive/news-single/article/dynamic-dns-und-strato.html

it works!

10

:+1: Have fun!

11

Even easier is to set a CNAME with your DNS-Hoster from collabora.domain.tld to cloud.domain.tld.
This keeps the reported IP always with the DDNS-account no matter what DDNS-Client you use.

It still is separated by virtual host entrys because the reported domain is still different in contrary to redirects.

12

Thanks. works good with the ddclient