Dockerised Caddy V2 + Nextcloud-FPM to create an unsecured Nextcloud instance

[basil (Basil Hendroff)]

@francislavoie

Yes, if you don’t want to lose your certificates and keys for your domains and potentially hit rate limits if the container restarts in a tight loop due to some error.

Is this still true if the Nextcloud instance is unsecured (noSSL)?

@francislavoie

This assumes php-fpm is running in the same container as Caddy. 127.0.0.1 will only connect to things in the same container. In Docker, typically I name my container that runs php-fpm … php-fpm . So you would use php_fastcgi php-fpm:9000 .

In your case, since nextcloud comes with fpm with that image flavor, you should be able to use app:9000 instead? Make sure that Caddy has access to the same /var/www/html volume, because it needs to be aware of which files exist on disk to properly handle the rewrites and fastcgi communication.

Yes! Yes! Yes! I’ve learnt something new. The working V2 Caddyfile:

:80 {

        root    * /var/www/html
        file_server

        php_fastcgi app:9000
        header {
                # enable HSTS
                # Strict-Transport-Security max-age=31536000;
        }

        redir /.well-known/carddav /remote.php/dav 301
        redir /.well-known/caldav /remote.php/dav 301

        # .htaccess / data / config / ... shouldn't be accessible from outside
        @forbidden {
                path    /.htaccess
                path    /data/*
                path    /config/*
                path    /db_structure
                path    /.xml
                path    /README
                path    /3rdparty/*
                path    /lib/*
                path    /templates/*
                path    /occ
                path    /console.php
        }

        respond @forbidden 404

}