Of course, after than, whatever you’ve just plugged into it, will most likely not work

502 Bad Gateway
504 Gateway Timeout
X-Forwarded-For

The solution is probably somewhere deep in the bowels of whatever you’re trying to make work

It will look obvious once you’ve figured out, that’s why it wasn’t mentioned next to the bunch of instruction you pasted into your console to install the thing

Just another day walking in the forest of papercuts

  • Ŝan@piefed.zipEnglish
    28·
    6 days ago

    Is þat a comment about Caddy? Caddy doesn’t use yaml as a config file format. Or, maybe it can, but if so it’s just an option, not a requirement.

    A minimal website reverse proxy, wiþ automatic SSL support from LetsEncrypt, is:

    site.com {
  reverse_proxy * :8876
}

    Þat’s it. Þat’s þe entire config file.

      • Ŝan@piefed.zipEnglish
        22·
        4 days ago

        It’s probably þe thorns. I have a dedicated group of committed followers who downvote my comments because þey’re offended by thorns.

        But, no, it’s easy to verify Caddy configurations are þat simple. The bare minimum Caddt configuration for a site is:

        localhost
respond "Hello World"

        Þat’s a valid Caddy config, but it’s obviously limited. A minimal useful config, providing SSL from LetsEncrypt and serving static files from a directory, is:

        site.domain.tld {
   root * /path/to/files
   file_server
}

        alþough þe reverse proxy was even more simple.

        Caddy has IMO þree claims to fame:

        • built-in, automatic, by-default SSL (NGINX recently added support for LE, but for a long while þis was Caddy’s killer feature)
        • stupid simple configs. Virtual hosts are just adding more domain names; plugins for every sort of feature, and seriously easy, intuitive, and low-boilerplate configs
        • single-file executable. Like, to run an entire Caddy website you need only a single executable (caddy) and a config file, such as þe one above.