Using Lets Encrypt Staging with AIO install

ℹ️ Support
, ,
1

I’m installing Nextcloud AIO on a Ubuntu VPS using the instructions here:

So I’m using this command:
sudo docker run \ --sig-proxy=false \ --name nextcloud-aio-mastercontainer \ --restart always \ --publish 80:80 \ --publish 8080:8080 \ --publish 8443:8443 \ --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \ --volume /var/run/docker.sock:/var/run/docker.sock:ro \ ghcr.io/nextcloud-releases/all-in-one:latest

I have hit the rate limit on letsencrypt.org. I would like to use their staging api (while I’m experimenting and testing). How do I do that? Is there a switch in the docker command? Can I edit some config file somewhere?

2

Use a test subdomain: What can I do when Nextcloud is not reachable via my domain or if I get `SSL_ERROR_INTERNAL_ERROR_ALERT` or `ERR_SSL_PROTOCOL_ERROR` when opening my Nextcloud domain? · nextcloud/all-in-one · Discussion #2105 · GitHub

3

Thanks Josh. I did see that. I believe there are also limits on subdomains and also on the email address tied to the registration. It’s an awkward work around. Simpler would be to just use the letsencrypt staging API (I believe certs are virtually unlimited). I’m hoping there is a way to do that.

4

Two options come to mind:

  • Use an external HTTPS reverse proxy instead of the AIO built-in one (you can then configure it however you want)
  • In theory you can modify the Caddyfile in the AIO apache container around here and add Caddy’s ca parameter to point at LE’s staging endpoint.
1 Like
5

I guess I’m getting my answer. No, there isn’t a switch. I’ll use the reverse proxy approach. Thanks for your help Josh.

1 Like
6

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.