For Mastodon Caddy Setting file. (Based on official Nginx configuration example) [Last Update: Mar 07, 2021]

Caddyfile.caddy1

https://yourdomain.example.com/ {
    log / /var/log/caddy/mastodon.log "{combined}" {
        rotate_age 90
    }
    root /home/mastodon/live/public
    gzip

    header / {
        Strict-Transport-Security "max-age=31536000"
    }

    header /sw.js Cache-Control "public, max-age=0"
    header /emoji Cache-Control "public, max-age=31536000, immutable"
    header /packs Cache-Control "public, max-age=31536000, immutable"
    header /system/accounts/avatars Cache-Control "public, max-age=31536000, immutable"
    header /system/media_attachments/files Cache-Control "public, max-age=31536000, immutable"

    errors {
        * 500.html
    }

    rewrite {
        if {path} is /
        to /proxy{path}
    }

    rewrite {
        if {path} not_has /api/v1/streaming
        to {path} /proxy{path}
    }

    proxy /proxy localhost:3000 {
        without /proxy

        transparent
        websocket
    }

    proxy /api/v1/streaming localhost:4000 {
        transparent
        websocket
    }

    tls your@mail-address.example.com
}

Caddyfile.caddy2

{
  email your@mail-address.example.com
}

https://yourdomain.example.com {
  @local {
    file
    not path /
  }
  @local_media {
    path_regexp /system/(.*)
  }
  @streaming {
    path /api/v1/streaming/*
  }
  @cache_control {
    path_regexp ^/(emoji|packs|/system/accounts/avatars|/system/media_attachments/files)
  }

  root * /home/mastodon/live/public
  log {
    output file /var/log/caddy/mastodon.log
  }

  encode zstd gzip

  handle_errors {
    rewrite 500.html
    file_server
  }

  header {
    Strict-Transport-Security "max-age=31536000"
  }
  header /sw.js Cache-Control "public, max-age=0"
  header @cache_control Cache-Control "public, max-age=31536000, immutable"

  handle @local {
    file_server
  }

  ## If you've been migrated media from local to object storage, this navigate old URL to new one.
  # redir @local_media https://yourobjectstorage.example.com/{http.regexp.1} permanent

  reverse_proxy @streaming {
    to http://localhost:4000

    transport http {
      keepalive 5s
      keepalive_idle_conns 10
    }
  }

  reverse_proxy  {
    to http://localhost:3000

    header_up X-Forwarded-Port 443
    header_up X-Forwarded-Proto https

    transport http {
      keepalive 5s
      keepalive_idle_conns 10
    }
  }
}

@rnaff I've put it up at https://gist.github.com/peterc/fef53e6a308d412ab793148a1808977a - I think it's pretty much the same as the one here.

It's for v1 or v2 caddy?

…

On Tue, Nov 22, 2022, 5:37 AM Peter Cooper ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ @rnaff <https://github.com/rnaff> I've put it up at https://gist.github.com/peterc/fef53e6a308d412ab793148a1808977a - I think it's pretty much the same as the one here. — Reply to this email directly, view it on GitHub <https://gist.github.com/bb7c90cbe628f216f821e835df1aeac1#gistcomment-4377869> or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARYHDOTFBGCOG7Q3LQNDUKLWJS5ATBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFQKSXMYLMOVS2I5DSOVS2I3TBNVS3W5DIOJSWCZC7OBQXE5DJMNUXAYLOORPWCY3UNF3GS5DZVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVA2DOMRTHAYDKMVHORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you were mentioned. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

FYI, line 14 on v2, seems incorrect. Its working for most clients, but certain libraries seem to be throwing strange errors (as they sometimes lack the last / on the end of the URL).

Needs changing from path /api/v1/streaming/* to path /api/v1/streaming*