Caddy & DuckDNS

A way to get https when portforwarding with bluebubbles

This guide is written with the intention caddy is deployed on the same mac as your bluebubbles server but the process is similar if you have a remote caddy server.


  • Works nonstandard ports


  • A duckdns account with a domain

  • A setup bluebubbles server

  • The ability to portforward your mac mini or reverse proxy to a machine that can be portforwarded (ex: aws, gcp, oracle, etc)

Steps to setup caddy

  1. Download caddy with duckns and move it to your home folder with the following command

Intel Macs:

curl -o ./caddy

Apple Silicon:

curl -o ./caddy

  1. Make caddy executable with the command chmod 755 ./caddy

  2. Download the template caddy file with the following command:

curl -o ./Caddyfile

  1. Edit the Caddyfile

  • replace the example domains with your domains

  • replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx with your duckdns token

  • Optional adjust the https/http or bluebubbles server ports as needed

  1. For testing purposes set your duckdns domain to the local ip of your bluebubbles server using the duckdns web portal

  1. test the config with ./caddy run

  2. if the config works and you can access your domain via https use ./caddy start to make it auto run

  3. Setup portforwarding (not covered in this guide)

  4. Optional install duckdns to your mac server in order to auto-update public ip


Guide created by @Deemo in the BlueBubbles Discord

Last updated