Fosstodon

Lukas RotermundI just added a custom caddy build with the cache handler in front of my `file_server`, which increased the response performance by 50%. Crazy!<a href="https://social.tchncs.de/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddy</a> <a href="https://social.tchncs.de/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a>

Lukas RotermundTake back control: secure and private self-hosting on Debian with SSH keys, an ufw firewall and a robust fail2ban configuration. Use Docker and Caddy as a reverse proxy to securely provide your self-hosted services.Step-by-step, minimal, and practical.<a href="https://lukasrotermund.de/posts/simple-private-self-hosting/" rel="nofollow noopener" translate="no" target="_blank">https://lukasrotermund.de/posts/simple-private-self-hosting/</a><a href="https://social.tchncs.de/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://social.tchncs.de/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://social.tchncs.de/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://social.tchncs.de/tags/DockerCompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#DockerCompose</a> <a href="https://social.tchncs.de/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a href="https://social.tchncs.de/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddy</a> <a href="https://social.tchncs.de/tags/ReverseProxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReverseProxy</a> <a href="https://social.tchncs.de/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://social.tchncs.de/tags/Webhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhosting</a> <a href="https://social.tchncs.de/tags/Server" class="mention hashtag" rel="nofollow noopener" target="_blank">#Server</a> <a href="https://social.tchncs.de/tags/Hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hosting</a>

Elias Probst<a href="https://san-junipero.gimme-sympathy.org/@gewt" class="u-url mention" rel="nofollow noopener" target="_blank">@gewt</a> move to <a href="https://mastodon.social/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> and there won't be a need for <a href="https://mastodon.social/tags/certbot" class="mention hashtag" rel="nofollow noopener" target="_blank">#certbot</a> anymore, since it comes with built-in <a href="https://mastodon.social/tags/ACME" class="mention hashtag" rel="nofollow noopener" target="_blank">#ACME</a> support and all tools and knobs one could wish for.It comes with many sane defaults and thereby allows to run quite complex setups - yet only requiring very minimal configs.<a href="https://caddyserver.com/" rel="nofollow noopener" translate="no" target="_blank">https://caddyserver.com/</a>

Scott Williams 🐧I have again tried and failed to get my <a href="https://mastodon.online/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nextcloud</a> server to be happy with <a href="https://mastodon.online/tags/caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyserver</a>. It seems others have gotten pretty URLs with a subdomain to work and I got it sort of half-working, in that it's showing a nextcloud page, but with no CSS and an otherwise page not found.My current ISP blocks port 80, so I have to use dns-01 with apache, which is one of those things that isn't great if I were to abruptly kick the bucket and my wife would eventually lose access to our server.

Matt WilliamsWant to leverage <a href="https://fosstodon.org/tags/MCP" class="mention hashtag" rel="tag">#MCP</a> (Model Context Protocol) without the hassle? Learn how to set up a powerful <a href="https://fosstodon.org/tags/n8n" class="mention hashtag" rel="tag">#n8n</a> server on <a href="https://fosstodon.org/tags/hostinger" class="mention hashtag" rel="tag">#hostinger</a> for <a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="tag">#AI</a> <a href="https://fosstodon.org/tags/automation" class="mention hashtag" rel="tag">#automation</a> with <a href="https://hachyderm.io/@tailscale" class="u-url mention">@tailscale</a> and <a href="https://fosstodon.org/tags/caddyserver" class="mention hashtag" rel="tag">#caddyserver</a> Save $200+ over 2 years with this method 🔧 <a href="https://youtu.be/OmWJPJ1CR7M" target="_blank" rel="nofollow noopener" translate="no">https://youtu.be/OmWJPJ1CR7M</a>

KielKontrovers Blog<a href="https://social.tchncs.de/@simsus" class="u-url mention" rel="nofollow noopener" target="_blank">@simsus</a> für den Fall finde ich ja den Webserver <a href="https://norden.social/tags/Caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddyserver</a> genial, der automatisch verlängert und auch automatisch beantragt:<a href="https://caddyserver.com/" rel="nofollow noopener" translate="no" target="_blank">https://caddyserver.com/</a><a href="https://infosec.exchange/@caddy" class="u-url mention" rel="nofollow noopener" target="_blank">@caddy</a>

RavenCaddy Web Server 2.10 released with encrypted ClientHello (ECH) support, post-quantum key exchange, ACME profiles, libdns 1.0 APIs, global DNS config<a href="https://github.com/caddyserver/caddy/releases/tag/v2.10.0" rel="nofollow noopener" translate="no" target="_blank">https://github.com/caddyserver/caddy/releases/tag/v2.10.0</a><a href="https://mastodon.bsd.cafe/tags/caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyserver</a> <a href="https://mastodon.bsd.cafe/tags/caddyreverseproxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyreverseproxy</a> <a href="https://mastodon.bsd.cafe/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#webserver</a> <a href="https://mastodon.bsd.cafe/tags/reverseproxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#reverseproxy</a> <a href="https://mastodon.bsd.cafe/tags/acme" class="mention hashtag" rel="nofollow noopener" target="_blank">#acme</a> <a href="https://mastodon.bsd.cafe/tags/postquantumcryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#postquantumcryptography</a>

Lanie Molinar CarmeloHi all. Hoping someone in the <a href="https://allovertheplace.ca/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> community can help. I'm trying to set up <a href="https://allovertheplace.ca/tags/Linkwarden" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linkwarden</a> in <a href="https://allovertheplace.ca/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> behind <a href="https://allovertheplace.ca/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddy</a>. The service is running, but I'm unable to create a user account. This is what I see in my browser console when I try:<pre><code>register:1 [Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113 register:1 [DOM] Input elements should have autocomplete attributes (suggested: "new-password"): (More info: https://www.chromium.org/developers/design-documents/create-amazing-password-forms) <input data-testid="password-input" type="password" placeholder="••••••••••••••" class="w-full rounded-md p-2 border-neutral-content border-solid border outline-none focus:border-primary duration-100 bg-base-100" value="tyq5ghp!QVH-mva1agc"> register:1 [DOM] Input elements should have autocomplete attributes (suggested: "new-password"): (More info: https://www.chromium.org/developers/design-documents/create-amazing-password-forms) <input data-testid="password-confirm-input" type="password" placeholder="••••••••••••••" class="w-full rounded-md p-2 border-neutral-content border-solid border outline-none focus:border-primary duration-100 bg-base-100" value="tyq5ghp!QVH-mva1agc"> Error api/v1/users:1 Request unavailable in the network panel, try reloading the inspected page Failed to load resource: the server responded with a status of 400 () Failed to load resource: the server responded with a status of 400 () </code></pre>compose file:<pre><code>services: postgres: image: postgres:16-alpine container_name: linkwarden_postgres env_file: .env restart: always volumes: - ./pgdata:/var/lib/postgresql/data networks: - linkwarden_net linkwarden: env_file: .env environment: - DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@linkwarden_postgres:5432/postgres restart: always # build: . # uncomment this line to build from source image: ghcr.io/linkwarden/linkwarden:latest # comment this line to build from source container_name: linkwarden ports: - 3009:3000 volumes: - ./data:/data/data networks: - linkwarden_net depends_on: - postgres networks: linkwarden_net: driver: bridge </code></pre>Relevant part of .env file:<pre><code>NEXTAUTH_URL=https://bookmarks.laniecarmelo.tech/api/v1/auth NEXTAUTH_SECRET=x8az9q9w8ofAxnrVcer2vsPHeMmKSPbf # Manual installation database settings # Example: DATABASE_URL=postgresql://user:password@localhost:5432/linkwarden DATABASE_URL= # Docker installation database settings POSTGRES_PASSWORD=redacted # Additional Optional Settings PAGINATION_TAKE_COUNT= STORAGE_FOLDER= AUTOSCROLL_TIMEOUT= NEXT_PUBLIC_DISABLE_REGISTRATION=false NEXT_PUBLIC_CREDENTIALS_ENABLED=true </code></pre>Caddyfile snippet<pre><code>*.laniecarmelo.tech { tls redacted { dns cloudflare redacted } header { Content-Security-Policy "default-src 'self' https: 'unsafe-inline' 'unsafe-eval'; img-src https: data:; font-src 'self' https: data:; frame-src 'self' https:; object-src 'none'" Referrer-Policy "strict-origin-when-cross-origin" Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" X-Content-Type-Options "nosniff" X-Xss-Protection "1; mode=block" } encode br gzip # Bookmarks @bookmarks host bookmarks.laniecarmelo.tech handle @bookmarks { reverse_proxy 127.0.0.1:3009 } } </code></pre>Can anyone help? I have no idea how to fix this. <a href="https://allovertheplace.ca/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://allovertheplace.ca/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://lemmy.ml/c/selfhost" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhost</a> <a href="https://lemmy.world/c/selfhosted" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhosted</a> <a href="https://a.gup.pe/u/selfhosting" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhosting</a>

Paul CampbellSwitching my Caddy server to use ZeroSSL for AMCE SSL certification, replacing LetsEncrypt, was as easy as adding this to my <code>Caddyfile</code>:<pre><code>{ acme_ca https://acme.zerossl.com/v2/DV90 } </code></pre><a class="hashtag" href="https://mitra.kemitix.net/collections/tags/caddyserver" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/caddy" rel="nofollow noopener" target="_blank">#Caddy</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/ssl" rel="nofollow noopener" target="_blank">#SSL</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/acme" rel="nofollow noopener" target="_blank">#ACME</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/letsencypt" rel="nofollow noopener" target="_blank">#LetsEncypt</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/zerossl" rel="nofollow noopener" target="_blank">#ZeroSSL</a>

Lanie Molinar CarmeloHi everyone, I'm encountering an issue with my self-hosted setup using Caddy 2.9.1 and Authelia 4.38.19. All domains except <code>auth.laniecarmelo.tech</code> return a 401 Unauthorized error. Journald logs suggest issues with insecure schemes (<code>''</code>) instead of <code>https</code> or <code>wss</code>.Details:<ul><li>Setup: Caddy as reverse proxy, Authelia for authentication</li><li>Domains: AdGuard Home, Forgejo, LinkAce, MiniFlux, TheLounge, Homepage, Beszel, Glances, Uptime Kuma, Tandoor Recipes, BookStack, Watchtower, Portainer</li><li>Logs: Authelia: <code>Feb 24 21:01:47 stormux authelia[2932]: level=error msg="Target URL '/' has an insecure scheme '', only 'https' and 'wss' are supported"</code>Caddy: <code>Feb 24 21:19:41 stormux caddy[48845]: {"msg":"handled request","method":"GET","host":"adguard.laniecarmelo.tech","status":200}</code></li></ul>Configurations: <ul><li>Full Caddyfile and Authelia config: <a href="https://gist.github.com/Lanie-Carmelo/fce9a7d6c984fc816475afee430f54a8" rel="nofollow noopener" target="_blank">GitHub Gist</a></li></ul>Curl Output: HTTP Request:<pre><code>$ curl home.laniecarmelo.tech -v < HTTP/1.1 308 Permanent Redirect < Location: https://home.laniecarmelo.tech/ </code></pre>HTTPS Request:<pre><code>$ curl https://home.laniecarmelo.tech -v < HTTP/2 401 < content-type: text/plain; charset=utf-8 < server: Caddy 401 Unauthorized </code></pre>Does anyone know what might be causing this? I suspect it could be related to <code>forward_auth</code> or trusted proxies.Thanks in advance! 🙏 <a href="https://allovertheplace.ca/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Authelia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authelia</a> <a href="https://allovertheplace.ca/tags/ReverseProxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReverseProxy</a> <a href="https://allovertheplace.ca/tags/TechHelp" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechHelp</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://lemmy.ml/c/selfhost" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhost</a> <a href="https://a.gup.pe/u/selfhosting" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhosting</a> <a href="https://lemmy.world/c/selfhosted" class="u-url mention" rel="nofollow noopener" target="_blank">@selfhosted</a>

alciregi :fedora:So, in the last times I started to self host various services on some <a href="https://social.linux.pizza/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> low end Virtual Private Servers around the world. For personal use. In the next days I will post a list of services I've deployed. I used rootless <a href="https://social.linux.pizza/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> containers. <a href="https://social.linux.pizza/tags/Podlet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podlet</a> in order to use dockerfiles whenever possible, and to create <a href="https://social.linux.pizza/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> services. And <a href="https://social.linux.pizza/tags/caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyserver</a> as frontend.

Lanie Molinar Carmelo🚨 Help Needed: <a href="https://allovertheplace.ca/tags/CORS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CORS</a> and <a href="https://allovertheplace.ca/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> Access Issues with <a href="https://allovertheplace.ca/tags/Nextflux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nextflux</a> + <a href="https://allovertheplace.ca/tags/MiniFlux" class="mention hashtag" rel="nofollow noopener" target="_blank">#MiniFlux</a> Setup 🚨Hi everyone! I’m struggling with a <a href="https://allovertheplace.ca/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> setup and could really use some advice from the self-hosting community. Lol I've been trying to figure this out for hours with no luck. Here’s my situation:Setup<ul><li>MiniFlux: Running in <a href="https://allovertheplace.ca/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> on a <a href="https://allovertheplace.ca/tags/RaspberryPi500" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi500</a> (<a href="https://allovertheplace.ca/tags/Stormux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stormux</a>, based on <a href="https://allovertheplace.ca/tags/ArchLinuxARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinuxARM</a>).</li><li>Nextflux: Hosted on Cloudflare Pages.</li><li>Reverse Proxy: <a href="https://allovertheplace.ca/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddy</a> (installed via AUR).</li><li>Cloudflare Access: Enabled for security and SSO.</li><li>Cloudflared: Also installed via AUR.</li><li>CORS Settings in Cloudflare Access: Configured to allow all origins, methods, and headers.</li></ul>What’s Working<ul><li>MiniFlux is accessible from my home network after removing restrictive CORS settings in both Caddy and MiniFlux.</li><li>Nextflux is properly deployed on Cloudflare Pages.</li></ul>The ProblemNextflux cannot connect to MiniFlux due to persistent CORS errors and authentication issues with Cloudflare Access. Here are the errors I’m seeing in the browser console:<ol><li>CORS Error:<code>Access to fetch at 'https://rss.laniecarmelo.tech/v1/me' from origin 'https://nextflux.laniecarmelo.tech' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.</code></li><li>Cloudflare Access Redirection:<pre><code>Request redirected to 'https://lifeofararebird.cloudflareaccess.com/cdn-cgi/access/login/rss.laniecarmelo.tech'. </code></pre></li><li>Failed to Fetch:<pre><code>Failed to fetch: TypeError: Failed to fetch. </code></pre></li></ol>What I’ve Tried<ol><li>Service Token Authentication:<ul><li>Generated a service token in Cloudflare Access for Nextflux.</li><li>Added <code>CF-Access-Client-Id</code> and <code>CF-Access-Client-Secret</code> headers in Caddy for <code>rss.laniecarmelo.tech</code>.</li><li>Updated Cloudflare Access policies to include a bypass rule for this service token.</li></ul></li><li>CORS Configuration:<ul><li>Tried permissive settings (<code>Access-Control-Allow-Origin: *</code>) in both Caddy and MiniFlux.</li><li>Configured Cloudflare Access CORS settings to allow all origins, methods, and headers.</li></ul></li><li>Policy Adjustments:<ul><li>Created a bypass policy for my home IP range and public IP.</li><li>Added an "Allow" policy for authenticated users via email/login methods.</li></ul></li><li>Debugging Logs:<ul><li>Checked Cloudflared logs, which show requests being blocked due to missing access tokens (<code>AccessJWTValidator</code> errors).</li></ul></li></ol>Current StateDespite these efforts:<ul><li>Requests from Nextflux are still being blocked by Cloudflare Access or failing due to CORS issues.</li><li>The browser console consistently shows "No 'Access-Control-Allow-Origin' header" errors.</li></ul>Goals<ol><li>Allow Nextflux (hosted on Cloudflare Pages) to connect seamlessly to MiniFlux (behind Cloudflare Access).</li><li>Maintain secure access to MiniFlux for other devices (e.g., my home network or mobile devices).</li></ol>My Environment<ul><li>Raspberry Pi 500 running Arch Linux ARM.</li><li>Both Caddy and Cloudflared are installed via AUR packages.</li><li>MiniFlux is running in Docker with the following environment variables:<code>CLOUDFLARE_SERVICE_AUTH_ENABLED=trueCLOUDFLARE_CLIENT_ID=<client-id>CLOUDFLARE_CLIENT_SECRET=<client-secret></code></li></ul>Relevant LogsFrom <code>cloudflared</code>:<pre><code>ERR error="request filtered by middleware handler (AccessJWTValidator) due to: no access token in request" </code></pre>From the browser console:<pre><code>Access to fetch at 'https://rss.laniecarmelo.tech/v1/me' has been blocked by CORS policy. </code></pre>Questions<ol><li>Is there a better way to configure CORS for this setup?</li><li>Should I be handling authentication differently between Nextflux and MiniFlux?</li><li>How can I ensure that requests from Nextflux include valid access tokens?</li></ol>Any help or advice would be greatly appreciated! 🙏<a href="https://allovertheplace.ca/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://allovertheplace.ca/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://allovertheplace.ca/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSS</a> <a href="https://allovertheplace.ca/tags/CORS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CORS</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/ArchLinuxARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinuxARM</a> <a href="https://allovertheplace.ca/tags/CloudflarePages" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudflarePages</a> <a href="https://allovertheplace.ca/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://allovertheplace.ca/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a>

lil5 :golang: 🚲 🇳🇱http://www.myproject.localhost:8080/ http://app.myproject.localhost:8080/ http://api.myproject.localhost:8080/TIL you can add subdomains to localhost & it will just work!Great for throwing a <a href="https://fosstodon.org/tags/CaddyServer" class="mention hashtag" rel="tag">#CaddyServer</a> in between you and your development containers, let it route to all the different services by domain.<a href="https://fosstodon.org/tags/WebDev" class="mention hashtag" rel="tag">#WebDev</a>

Esparta :ruby:<a href="https://ruby.social/@nshki" class="u-url mention" rel="nofollow noopener" target="_blank">@nshki</a> that's something I've been telling everybody literally for years*: <a href="https://ruby.social/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> is the best thing anyone can use for a web server.<a href="https://caddyserver.com/" rel="nofollow noopener" translate="no" target="_blank">https://caddyserver.com/</a>* I'd link to where I said that before, but my decency prohibits me do that, so here's an screenshot instead.

BeanieBarrowMade my personal website get the maximum amount of points of Mozilla's HTTP Observatory. Now, my static site delivers content as securely as it possibly can. I highly recommend anyone with a personal website to tweak it along with their webserver so that it gets at least a hundred points on HTTP Observatory. <a href="https://developer.mozilla.org/en-US/observatory" rel="nofollow noopener" translate="no" target="_blank">https://developer.mozilla.org/en-US/observatory</a> The least you can do is add your site to the HSTS Preload list (<a href="https://hstspreload.org/" rel="nofollow noopener" translate="no" target="_blank">https://hstspreload.org/</a>).<a href="https://mastodon.grin.hu/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://mastodon.grin.hu/tags/personalwebsite" class="mention hashtag" rel="nofollow noopener" target="_blank">#personalwebsite</a> <a href="https://mastodon.grin.hu/tags/mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#mozilla</a> <a href="https://mastodon.grin.hu/tags/mdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#mdn</a> <a href="https://mastodon.grin.hu/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> <a href="https://mastodon.grin.hu/tags/caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyserver</a> <a href="https://mastodon.grin.hu/tags/hsts" class="mention hashtag" rel="nofollow noopener" target="_blank">#hsts</a> <a href="https://mastodon.grin.hu/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a>

Robert Rudolf<a href="https://sopuli.xyz/u/IsoKiero" class="u-url mention">@IsoKiero</a> I'm a happy user of <a href="https://fosstodon.org/tags/MailCow" class="mention hashtag" rel="tag">#MailCow</a> for years. It just works, simple to inslall and update. I'm using <a href="https://fosstodon.org/tags/CaddyServer" class="mention hashtag" rel="tag">#CaddyServer</a> as a reverse proxy to further simplify the setup. And it's made in <a href="https://fosstodon.org/tags/EU" class="mention hashtag" rel="tag">#EU</a> 😄

Mirko LenzFor anyone wanting to add custom plugins/modules to <a href="https://fosstodon.org/tags/caddyserver" class="mention hashtag" rel="tag">#caddyserver</a> on <a href="https://fosstodon.org/tags/NixOS" class="mention hashtag" rel="tag">#NixOS</a>: <a href="https://hachyderm.io/@vbernat" class="u-url mention">@vbernat</a> released a flake to do this via xcaddy in a fixed-output derivation. Switched to it on my server today and works perfectly! More details in his blog post:<a href="https://vincent.bernat.ch/en/blog/2024-caddy-nix-plugins" target="_blank" rel="nofollow noopener" translate="no">https://vincent.bernat.ch/en/blog/2024-caddy-nix-plugins</a>

lil5 :golang: 🚲 🇳🇱<a href="https://caddy.community/t/set-cookie-manipulation-in-reverse-proxy/7666/15" target="_blank" rel="nofollow noopener" translate="no">https://caddy.community/t/set-cookie-manipulation-in-reverse-proxy/7666/15</a><a href="https://fosstodon.org/tags/CaddyServer" class="mention hashtag" rel="tag">#CaddyServer</a> is able to alter cookies that are passed between a reverse proxy, removing pesky browser restriction

Allen:hacker_u: :hacker_i: <a href="https://social.tchncs.de/tags/caddyserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddyserver</a> <a href="https://social.tchncs.de/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#music</a>

Lukas RotermundI retired NGINX for Caddy - and never looked back.In my last blog post, I reported on a DoS attack and Docker's dangerous default behaviour regarding ufw and setting up NGINX locally.<a href="https://fosstodon.org/@lil5" class="u-url mention" rel="nofollow noopener" target="_blank">@lil5</a> pointed me to the Caddy web server after my post, and I migrated everything to it shortly afterwards.My latest blog post is about migrating from NGINX to Caddy and why I don't want to go back to NGINX.<a href="https://lukasrotermund.de/posts/i-retired-nginx-for-caddy-and-never-looked-back/" rel="nofollow noopener" translate="no" target="_blank">https://lukasrotermund.de/posts/i-retired-nginx-for-caddy-and-never-looked-back/</a><a href="https://social.tchncs.de/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddy</a> <a href="https://social.tchncs.de/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#CaddyServer</a> <a href="https://social.tchncs.de/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#NGINX</a>

Recent searches

Search options

Administered by:

Server stats:

#caddyserver