# Collabora & Nextcloud -\> HTTPS & Local Domains & Arambian & NanoPi R4S ARM64

**URL:** <https://forum.collaboraonline.com/t/collabora-nextcloud-https-local-domains-arambian-nanopi-r4s-arm64/3606>\
**Category:** Installation & Configuration\
**Created:** [April 14, 2025, 1:11pm UTC](https://forum.collaboraonline.com/t/collabora-nextcloud-https-local-domains-arambian-nanopi-r4s-arm64/3606 "2025-04-14T13:11:41Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![v1k691](https://avatars.discourse-cdn.com/v4/letter/v/90db22/32.png) [@v1k691](https://forum.collaboraonline.com/u/v1k691)\
**Post date:** [April 14, 2025, 1:11pm UTC](https://forum.collaboraonline.com/t/collabora-nextcloud-https-local-domains-arambian-nanopi-r4s-arm64/3606/1 "2025-04-14T13:11:41Z")

</div>

Hi Everybody,

I’m trying to set up Nextcloud with Collabora Office on my NanoPi R4S running Armbian, but I’m having trouble configuring the reverse proxy (nginx/Caddy) for HTTPS with local domains.  
Current Setup:

```
Running via docker-compose.yml (shown below)

Without HTTPS, everything works: Collabora can open documents in Nextcloud's web UI

With HTTPS enabled, Collabora integration breaks

Added to /etc/hosts:
Copy

127.0.0.1 nextcloud.lan collabora.nextcloud.lan

```

What I Need:

```
HTTPS configuration for both services

Reverse proxy to local domains:

    Nextcloud: https://nextcloud.lan

    Collabora: https://collabora.nextcloud.lan

```

My docker-compose.yml (HTTP-only version):

networks:  
network:  
driver: bridge

volumes:  
mariadb\_config:  
mariadb\_data:  
nextcloud\_config:  
nextcloud\_data:

services:  
collabora:  
image: collabora/code  
restart: unless-stopped  
container\_name: collabora  
hostname: collabora  
domainname: collabora.nextcloud.lan  
networks:  
- network  
ports:  
- “9980:9980”  
cap\_add:  
- MKNOD

nextcloud\_db:  
image: linuxserver/mariadb  
restart: unless-stopped  
container\_name: nextcloud\_db  
hostname: nextcloud\_db  
networks:  
- network  
volumes:  
- mariadb\_config:/config  
- mariadb\_data:/data  
environment:  
- PUID=1000  
- PGID=1000  
- TZ=UTC  
- MYSQL\_ROOT\_PASSWORD=nextcloud  
- MYSQL\_DATABASE=nextcloud\_db  
- MYSQL\_USER=nextcloud  
- MYSQL\_PASSWORD=nextcloud

nextcloud:  
image: linuxserver/nextcloud  
restart: unless-stopped  
depends\_on:  
- nextcloud\_db  
- collabora  
container\_name: nextcloud  
hostname: nextcloud  
domainname: nextcloud.lan  
networks:  
- network  
ports:  
- “8080:80”  
volumes:  
- nextcloud\_config:/config  
- nextcloud\_data:/data  
environment:  
- PUID=1000  
- PGID=1000  
- TZ=UTC  
- NEXTCLOUD\_UPLOAD\_LIMIT=16G  
- NEXTCLOUD\_MAX\_TIME=3600  
- NEXTCLOUD\_MEMORY\_LIMIT=3G  
- SKIP\_DOMAIN\_VALIDATION=true  
- NEXTCLOUD\_TRUSTED\_DOMAINS=nextcloud.lan

Key Questions:

```
How should I modify the docker-compose.yml to:

    Enable HTTPS for both services?

    Properly configure the reverse proxy for the local domains?

    Set up valid SSL certificates for *.lan domains?

For Collabora:

    What extra_params or environment variables are needed for HTTPS?

    How to configure Nextcloud's config.php for the Collabora HTTPS endpoint?

```

I’d prefer a solution using Caddy if possible, as it’s simpler for automatic HTTPS. Any working configuration examples would be greatly appreciated!

Thanks in advance for your help!

Viktor Malygin  
WordPress Developer  
[https://vm-project.pro](https://vm-project.pro)

---

_[View the full topic](https://forum.collaboraonline.com/t/collabora-nextcloud-https-local-domains-arambian-nanopi-r4s-arm64/3606)._