I am one step closer from changing my standalone self-hosted services to a k3s cluster.
I have another VPS where I (painfully) installed #openSUSE Tumbleweed and installed #k3s
Spent the entire afternoon trying to figure out #caddy ingress controller and #certmanager
Now I just need to find #helm charts for the services I want to host!
#opensuse #k3s #caddy #certmanager #helm
Killed the night at my #homelab trying to get all my caddy installations reporting to Prometheus so I can get my grafana dashboards looking sick!... Why, I don't know! I never look at it. 🤨
#homelab #selfhosted #selfhosting #caddy #minilab
@MartinGuay ufw and fail2ban is an epic combo.
If you’re using caddy remember to add a #caddy conf to #fail2ban
https://muetsch.io/how-to-integrate-caddy-with-fail2ban.html
📬 Freiheit muss nichts kosten: Open Source Tools vorgestellt
#Empfehlungen #Softwareentwicklung #Caddy #exa #FairEmail #FreieSoftware #github #neosay #OpenSource #Screego #Thumbkey https://tarnkappe.info/artikel/empfehlungen/open-source-freiheit-muss-nichts-kosten-279923.html
#empfehlungen #softwareentwicklung #caddy #exa #fairemail #freiesoftware #github #neosay #opensource #screego #thumbkey
Updated the website. Now, the installation guide is more helpful for server administration novices and addresses the v1.0.0 installation issue:
https://betula.mycorrhiza.wiki/installation.html
There is also a new guide for setting up HTTPS with #nginx:
https://betula.mycorrhiza.wiki/https-domain.html
A guide for #Caddy will be written soon.
I am kinda new to caddy so I created a question in caddy forum
https://caddy.community/t/reverse-proxy-with-local-dns/20908
@zekjur since i am using gokrazy maybe you could help me? Thanks in advance ^^
If someone wants to give me a 15-20 minute live course in how to make a dockerized Caddy reverse proxy play nice with dockerized web-apps over tailscale, let me know! I think I've taken water over my head when it comes to choosing challenges in technology stacking... 🤯
Just upgraded to #Caddy 2.7.2 on FreshBSD.org. It didn't last very long:
Successfully started Caddy (pid=15076) - Caddy is running in the background
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x907c10]
Looks like it's HTTP/3 related, which I've disabled for now: https://github.com/caddyserver/caddy/issues/5680
Imagine inventing a programming language in 2009 and it still does this sort of thing...
yeah #caddy way better using less cpu to handle more... even handling most of the traffic when it was the only backend for a few minutes it was still less
trying #nginx instead of #caddy on the third server. notable observations:
1. it appears nginx buffers to fs instead of memory, giving the illusion of low memory usage while putting unnecessary wear on the storage device while it indirectly uses the memory anyway as fs cache.
2. with nginx the RX is many times more than the TX; I'm afraid it's continuing to download the entirety of the file after the client aborts the connection.
3...
Actuellement, mes serveurs bannissent les IP repérées comme des #bots malveillants d'un coup de #firewall. J'aimerais remplacer ce ban par
- un ban sur tous les ports sauf http(s)
- une page html d'erreur qui explique ce qui cause le ban sur http(s)
Est-ce que vous avez des snippets en #nginx+lua+fichier de deny-list, ou via l'API de #caddy, pour arriver à ces fins ?
Merci bisous
Soweit so gut, mein Setup #caddy und #vaultwarden als #rootless #podman Container als #systemd service läuft schon ein paar Tage stabil. Backups werden täglich durchgeführt und via #borgbackup in eine #Hetzner storage box gesichert.
Wer mehr wissen will:
https://codeberg.org/EinApfelBaum/ansible.podman-01
#caddy #vaultwarden #rootless #podman #systemd #borgbackup #hetzner
Top 10 Golf Strategies and Plays That Can Help Improve Performance https://www.fogolf.com/555804/top-10-golf-strategies-and-plays-that-can-help-improve-performance/
#caddy #countryclub #Golf #GolfSkills #golfskillsvideos #golfskillsvlog #golfskillsYouTube #GolfStrategies #golfstrategiesvideos #golfstrategiesvlog #golfstrategiesYouTube #GolfTactics #golftacticsvideos #golftacticsvlog #golftacticsYouTube #golfing #Improve #Masters #Performance #pga #Plays #Strategies #summer #top #wpga
#caddy #countryclub #golf #golfskills #golfskillsvideos #golfskillsvlog #golfskillsyoutube #golfstrategies #golfstrategiesvideos #golfstrategiesvlog #golfstrategiesyoutube #golftactics #golftacticsvideos #golftacticsvlog #golftacticsyoutube #golfing #improve #masters #performance #pga #plays #strategies #summer #top #wpga
Maybe someone has an idea:
#caddy and #vaultwarden are running as a #podman container in a pod. I can access vaultwarden behind the reverse proxy.
After restarting the caddy container, I can no longer access vaultwarden. In caddy access log I can see the request and the status 502. so caddy can not reach the vaultwarden container.
After restarting the vaultwarden container , I can access vaultwarden again.
Running caddy 2.7 and vaultwarden 1.29.0
Just one of these nerdy questions about #selfhost I want to setup a docker-compose.yml with my own combination. #nextcloud with #fpm #redis and #postgresql but I don't want integrated proxy. I use a #caddy proxy installed through repo and not as a container, I don't want to mess up my other containers with a second proxy.
Web searches only provide full solutions or combinations with mariaDB or without redis. Rewriting these end up with not working states and even the logs don't show errors.
#selfhost #nextcloud #fpm #redis #postgresql #caddy
A quick half hour play and I've replaced my only docker app, nginxproxymanager.com, with #caddy and 60 lines of config.
Amazed it just works (and just works well).