Flipboard

0 posts0 participants0 posts today

Lanie Molinar CarmeloHi all. Hoping someone in the <a href="https://allovertheplace.ca/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Linkwarden</a> in <a href="https://allovertheplace.ca/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a> behind <a href="https://allovertheplace.ca/tags/Caddy" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#SelfHosted</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a> <a href="https://allovertheplace.ca/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a> <a href="https://lemmy.ml/c/selfhost" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@selfhost</a> <a href="https://lemmy.world/c/selfhosted" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@selfhosted</a> <a href="https://a.gup.pe/u/selfhosting" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@selfhosting</a>

LavX NewsFortifying Your Self-Hosted Services: Mitigating Man-in-the-Middle Attacks with CAA RecordsAs cyber threats evolve, understanding how to protect your self-hosted services becomes crucial. This article explores a recent Man-in-the-Middle attack on jabber.ru and demonstrates how to leverage C...<a href="https://news.lavx.hu/article/fortifying-your-self-hosted-services-mitigating-man-in-the-middle-attacks-with-caa-records" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/fortifying-your-self-hosted-services-mitigating-man-in-the-middle-attacks-with-caa-records</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://mastodon.cloud/tags/LetEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LetEncrypt</a> <a href="https://mastodon.cloud/tags/CAARecords" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CAARecords</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 noreferrer" 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 noreferrer" target="_blank">#SelfHosting</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Authelia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authelia</a> <a href="https://allovertheplace.ca/tags/ReverseProxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReverseProxy</a> <a href="https://allovertheplace.ca/tags/TechHelp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechHelp</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/HomeLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HomeLab</a> <a href="https://lemmy.ml/c/selfhost" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@selfhost</a> <a href="https://a.gup.pe/u/selfhosting" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@selfhosting</a> <a href="https://lemmy.world/c/selfhosted" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#podman</a> containers. <a href="https://social.linux.pizza/tags/Podlet" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#systemd</a> services. And <a href="https://social.linux.pizza/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> as frontend.

Lanie Molinar Carmelo🚨 Help Needed: <a href="https://allovertheplace.ca/tags/CORS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CORS</a> and <a href="https://allovertheplace.ca/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a> Access Issues with <a href="https://allovertheplace.ca/tags/Nextflux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nextflux</a> + <a href="https://allovertheplace.ca/tags/MiniFlux" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Docker</a> on a <a href="https://allovertheplace.ca/tags/RaspberryPi500" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi500</a> (<a href="https://allovertheplace.ca/tags/Stormux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stormux</a>, based on <a href="https://allovertheplace.ca/tags/ArchLinuxARM" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#SelfHosting</a> <a href="https://allovertheplace.ca/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a> <a href="https://allovertheplace.ca/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://allovertheplace.ca/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a> <a href="https://allovertheplace.ca/tags/RSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RSS</a> <a href="https://allovertheplace.ca/tags/CORS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CORS</a> <a href="https://allovertheplace.ca/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://allovertheplace.ca/tags/ArchLinuxARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ArchLinuxARM</a> <a href="https://allovertheplace.ca/tags/CloudflarePages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudflarePages</a>

LavX NewsEnhance Your Web Security with the Caddy Defender PluginThe Caddy Defender plugin offers a powerful middleware solution for web developers looking to protect their applications from unwanted traffic and safeguard AI training data. With features like IP ran...<a href="https://news.lavx.hu/article/enhance-your-web-security-with-the-caddy-defender-plugin" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/enhance-your-web-security-with-the-caddy-defender-plugin</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/WebSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebSecurity</a> <a href="https://mastodon.cloud/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://mastodon.cloud/tags/Middleware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Middleware</a>

RavenToday I switched my web server from Apache httpd to Caddy on FreeBSD 14. I've never seen a simpler web server. All you need is one Caddyfile to manage Caddy itself and all websites.<a href="https://mastodon.bsd.cafe/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a>

Paco Hope #resistFunny. I got some <a href="https://infosec.exchange/tags/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#spam</a> from <a href="https://infosec.exchange/tags/salesforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#salesforce</a> and went to click the 'unsubscribe' link. Nice to know that <a href="https://infosec.exchange/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> is what they use. But, uh, not very effective at unsubscribing.

Robert Rudolf<a href="https://sopuli.xyz/u/IsoKiero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@IsoKiero</a> I'm a happy user of <a href="https://fosstodon.org/tags/MailCow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#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="nofollow noopener noreferrer" target="_blank">#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="nofollow noopener noreferrer" target="_blank">#EU</a> 😄

Mirko LenzFor anyone wanting to add custom plugins/modules to <a href="https://fosstodon.org/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> on <a href="https://fosstodon.org/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a>: <a href="https://hachyderm.io/@vbernat" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@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" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vincent.bernat.ch/en/blog/2024-caddy-nix-plugins</a>

Allen:hacker_u: :hacker_i: <a href="https://social.tchncs.de/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> <a href="https://social.tchncs.de/tags/music" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Caddy</a> <a href="https://social.tchncs.de/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> <a href="https://social.tchncs.de/tags/NGINX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGINX</a>

Emanuele Panz"I recreated the server, now with encrypted disks, and restored the application. Can you check why it is not running?"Spent considerable time checking the <a href="https://phpc.social/tags/Symfony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Symfony</a>, <a href="https://phpc.social/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> and <a href="https://phpc.social/tags/phpfpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#phpfpm</a> configs: nothing could explain such errors, including not respecting any config change.It was the usual suspect: <a href="https://phpc.social/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selinux</a>, which was non properly configuredBonus point: took the time to quickly upgrade to PHP 8.3 and Symfony 6.4; not bad for an application last deployed on December 2022 ☺

Kévin DunglasOn December 5 and 6, I'll be in Vienna for SymfonyCon! I'll be explaining how HTTP compression works and how to use the latest developments in the field (Brotli, Zstandard...) to make your <a href="https://mastodon.social/@symfony" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@symfony</a> applications even faster.Of course, we'll also talk about how <a href="https://mastodon.social/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a> and <a href="https://mastodon.social/tags/FrankenPHP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FrankenPHP</a> can help (as always)!

Elias Probst<a href="https://chaos.social/@alios" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alios</a> I don't know whether there's a module for a fully declarative self-contained CA in <a href="https://mastodon.social/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixpkgs</a>, but you could run your own CA using "services.step-ca" and retrieve certs via <a href="https://mastodon.social/tags/ACME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ACME</a> (either through the corresponding applications' support or using "security.acme").If you're using <a href="https://mastodon.social/tags/CaddyServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaddyServer</a>, you also might want to simply use its built-in support to run an ACME CA (also based on smallstep) or utilize its ACME support to automatically retrieve certs at runtime for all defined hosts.

chris@strafpla.netBecause the excellent (and beloved for a decade or so) <a href="https://mstdn.strafpla.net/tags/reeder" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reeder</a> by <a href="https://gloria.social/@rizzi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rizzi</a> does not support <a href="https://mstdn.strafpla.net/tags/TLSClientAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLSClientAuth</a> for feeds* I spent a few hours on Yak-Shaving and on learning about <a href="https://mstdn.strafpla.net/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> <a href="https://mstdn.strafpla.net/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>-<a href="https://mstdn.strafpla.net/tags/resolved" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#resolved</a> and - in the end - about <a href="https://mstdn.strafpla.net/tags/iCloudPrivateRelay" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iCloudPrivateRelay</a>. If a local request is handled like an external request it may be because ... it's coming in as an external request. ___ * I’m sure I’m the only one left on the planet who has rss feeds with Client Certificates, so this is fine!

Mitex LeoAfter a lot of trial and error, I finally got object storage configured for this instance. I had originally planned to use Backblaze, but ended up going with Linode Object Storage. Unfortunately, the guides I found online didn't work for me, and I also had to make the switch from Caddy to Nginx. I'm thinking about writing a blog post to share my experience.<a href="https://mitexleo.one/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastoadmin</a> <a href="https://mitexleo.one/tags/fedimin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedimin</a> <a href="https://mitexleo.one/tags/fediadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediadmin</a> <a href="https://mitexleo.one/tags/s3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#s3</a> <a href="https://mitexleo.one/tags/linode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linode</a> <a href="https://mitexleo.one/tags/backblaze" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backblaze</a> <a href="https://mitexleo.one/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://mitexleo.one/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> <a href="https://mitexleo.one/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a>

Mitex LeoI'm using Caddy and couldn't find a guide to set up object cache proxying. Can someone please provide a Caddyfile for this? I'm using Backblaze for storage.<a href="https://mitexleo.one/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastoadmin</a> <a href="https://mitexleo.one/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a> <a href="https://mitexleo.one/tags/fediadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediadmin</a> <a href="https://mitexleo.one/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a>

teledyn 𓂀Today’s <a href="https://mstdn.ca/tags/apache2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apache2</a> puzzle: a machine on one domain needs to reverse proxy for a LAN machine on a different domain, so I need to also proxy the certificate which sounds like something that shouldn't be allowed, but perhaps there's a trick?I'm really just wanting to build a dev <a href="https://mstdn.ca/tags/mobilizon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mobilizon</a> <a href="https://mstdn.ca/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> for that other domain, and I could just put it on strange ports, but proxying seemed more elegant and elsewheres useful. <a href="https://mstdn.ca/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

teledyn 𓂀First question: if I attempt to migrate my rpi4B+ to <a href="https://mstdn.ca/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> from Apache2, am I headed for heartache?Second question is technical: I have one domain with a static page site that redirects a sub-path to WordPress and that same <a href="https://mstdn.ca/tags/letsencrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#letsencrypt</a> cert must also be combined full-chain+key put elsewhere as a PEM file for <a href="https://mstdn.ca/tags/icecast2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#icecast2</a>. Is this triple-app coverage for one cert doable with caddy?I presently build the icecast2 cert by hand every ninety days, which is a pain. There must be a better way.

Recent searches

Search options

Administered by:

Server stats:

#caddyserver