Shakedown Social

:projetstodon: ShalienWell installing <a href="https://mastodon.projetretro.io/tags/Brotli" class="mention hashtag" rel="nofollow noopener" target="_blank">#Brotli</a> on <a href="https://mastodon.projetretro.io/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#NGINX</a> IS A <a href="https://mastodon.projetretro.io/tags/PITA" class="mention hashtag" rel="nofollow noopener" target="_blank">#PITA</a> like really

MynacolI finally tried to replace <a class="hashtag" href="https://social.mynacol.xyz/tag/openssl" rel="nofollow noopener" target="_blank">#openssl</a> with <a class="hashtag" href="https://social.mynacol.xyz/tag/aws" rel="nofollow noopener" target="_blank">#aws</a>-lc on some of my services. Unfortunately, <a class="hashtag" href="https://social.mynacol.xyz/tag/nginx" rel="nofollow noopener" target="_blank">#nginx</a> and <a class="hashtag" href="https://social.mynacol.xyz/tag/mosquitto" rel="nofollow noopener" target="_blank">#mosquitto</a> lack support for it. Instead, I successfully switched <a class="hashtag" href="https://social.mynacol.xyz/tag/bind" rel="nofollow noopener" target="_blank">#BIND</a> to use aws-lc.I later also noticed that the rustls compatibility shim is in nixpkgs 25.05, but here BIND is missing some variables. And despite the wrapper being explicitly made for nginx, it also fails here with<pre><code>/nix/store/mkvc0lnnpmi604rqsjdlv1pmhr638nbd-binutils-2.44/bin/ld: objs/src/stream/ngx_stream_ssl_module.o: in function `ngx_stream_ssl_servername': /build/nginx-1.28.0/src/stream/ngx_stream_ssl_module.c:606:(.text+0xd59): undefined reference to `SSL_SESSION_get0_hostname' </code></pre>A shame. I wanted to change to more modern libraries.Untested: dovecot and postfix (they lack a <code>services.(dovecot2/postfix).package</code> variable to easily change the used package. A PR for dovecot is already open to add support for it.

Adam - K3CANI got some feedback about how slow my <a href="https://social.k3can.us/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> is to load. I decided to try my hand at setting up an <a href="https://social.k3can.us/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://social.k3can.us/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> so that the requests can be satisfied by the cache instead of being generated by the blog software itself.Just doing a few quick tests myself, it seems the like responses come a bit quicker, but I still think some of the delay is just due to the garbage residential Spectrum service.If anyone would like to poke at my blog and share any observations on load time and potential cache performance, that'd be cool. :-) <a href="https://social.k3can.us/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://social.k3can.us/tags/selfhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhost</a> <a href="https://social.k3can.us/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a>

:projetstodon: ShalienDear <a href="https://mastodon.projetretro.io/tags/fediadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediadmin</a>, regarding the current ongoing full force assault on our services by AI scrappers with all the risks associated (costs, services stability, data being stolen and so on) I can only recommend the setting up of <a href="https://mastodon.projetretro.io/tags/techaro" class="mention hashtag" rel="nofollow noopener" target="_blank">#techaro</a> <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#anubis</a> requests filter to "weight the souls of incoming HTTP requests"I tested it so far on <a href="https://mastodon.projetretro.io/tags/alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpine</a> <a href="https://mastodon.projetretro.io/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> deployed services with either <a href="https://mastodon.projetretro.io/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddy</a> , <a href="https://mastodon.projetretro.io/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> / <a href="https://mastodon.projetretro.io/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#httpd</a> and <a href="https://mastodon.projetretro.io/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> for the following services <a href="https://mastodon.projetretro.io/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a>, <a href="https://mastodon.projetretro.io/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a>, <a href="https://mastodon.projetretro.io/tags/forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#forgejo</a>, <a href="https://mastodon.projetretro.io/tags/lemmy" class="mention hashtag" rel="nofollow noopener" target="_blank">#lemmy</a>, <a href="https://mastodon.projetretro.io/tags/funkwhale" class="mention hashtag" rel="nofollow noopener" target="_blank">#funkwhale</a>, <a href="https://mastodon.projetretro.io/tags/bookwyrm" class="mention hashtag" rel="nofollow noopener" target="_blank">#bookwyrm</a> and a <a href="https://mastodon.projetretro.io/tags/minecraft" class="mention hashtag" rel="nofollow noopener" target="_blank">#minecraft</a> <a href="https://mastodon.projetretro.io/tags/mapviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#mapviewer</a> with little hassle and no big issuesFollowing the use of <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#anubis</a>, all scrapper (AI and regular) logs dropped drastically and bandwitch usage was cut by two third on the mastodon instance and half for the others servicesDo yourself and your users a favor try it : <a href="https://github.com/TecharoHQ/anubis" rel="nofollow noopener" translate="no" target="_blank">https://github.com/TecharoHQ/anubis</a>

Elena Rossini on GoToSocial ⁂Update no.2: It turns out, I cannot install <a href="https://aseachange.com/tags/varnishcache" class="mention hashtag" rel="nofollow noopener" target="_blank">#VarnishCache</a> on my shared hosting plan because that requires <a href="https://aseachange.com/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> and my plan doesn't support it... The only option I have - to manually install Varnish - is to move my <a href="https://aseachange.com/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wordpress</a> site from my shared hosting plan to a <a href="https://aseachange.com/tags/vps" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a>. I already have 2 VPS's so it would cost me nothing but this takes a bazillion steps and I honestly don't want to do it 😐 I love the Dashboard / ease of use of my shared hosting plan vis-à-vis Wordpress. Plan C is seeing if things are different with BunnyCDN. Plan Z is moving all my blogging efforts to Ghost but I don't want do to that. I'll try anything to protect my Wordpress site against the Mastodon stampede. Edit: for context, I have had this Wordpress site since 2010 (15 years now!) so I don't want to mess with it. cc: <a href="https://fosstodon.org/@cleantext" class="u-url mention" rel="nofollow noopener" target="_blank">@cleantext</a> and <a href="https://tech.lgbt/@ck0" class="u-url mention" rel="nofollow noopener" target="_blank">@ck0</a> (who asked about this)

JamieIt took a while to get my head around as I’m a complete noob at it, but this afternoon I’ve got Docker and Portainer setup and a container running Nginx. Also got a cronjob running every 10 minutes to automatically update DNS records in Cloudflare whenever it detects my public IP at home has updated. 😎<a href="https://gamerstavern.online/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://gamerstavern.online/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> <a href="https://gamerstavern.online/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://gamerstavern.online/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://gamerstavern.online/tags/Portainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Portainer</a> <a href="https://gamerstavern.online/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> <a href="https://gamerstavern.online/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a>

Martin Boller :debian: :tux: :freebsd: :windows: :mastodon:Another short blog post on blocking <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://infosec.exchange/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLM</a> <a href="https://infosec.exchange/tags/Bots" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bots</a> that slow down a website. Using <a href="https://infosec.exchange/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#NGINX</a>, but easily adaptable to <a href="https://infosec.exchange/tags/ApacheWebServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#ApacheWebServer</a> <a href="https://infosec.exchange/tags/Caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Caddy</a> etc<a href="https://www.infosecworrier.dk/blog/2025/07/botblocker/" rel="nofollow noopener" translate="no" target="_blank">https://www.infosecworrier.dk/blog/2025/07/botblocker/</a>

Jesse SkinnerI'm thinking of developing a new course or workshop in the fall.. would any of these interest you?<a href="https://toot.cafe/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://toot.cafe/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#svelte</a> <a href="https://toot.cafe/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a> <a href="https://toot.cafe/tags/css" class="mention hashtag" rel="nofollow noopener" target="_blank">#css</a> <a href="https://toot.cafe/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://toot.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://toot.cafe/tags/lua" class="mention hashtag" rel="nofollow noopener" target="_blank">#lua</a> <a href="https://toot.cafe/tags/freelancer" class="mention hashtag" rel="nofollow noopener" target="_blank">#freelancer</a>

Third spruce tree on the leftOh snap! `YARR - Yet Another RSS Reader` has a new version and I missed it in March! <a href="https://github.com/nkanaev/yarr/releases/tag/v2.5" rel="nofollow noopener" translate="no" target="_blank">https://github.com/nkanaev/yarr/releases/tag/v2.5</a> YARR is like Feedly or NewsBlur, except more like TinyRSS or FreshRSS - you can self-host. UNLIKE those, you can tell yarr to run at `<ip:port>`, so you can stick it at port 7666 for your reverse <a href="https://mas.to/tags/proxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxy</a>. And its lightweight, I run my own AND 3 other instances for fam. members on the same host accessed via different subdomains re-proxied by <a href="https://mas.to/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a>. <a href="https://mas.to/tags/rss" class="mention hashtag" rel="nofollow noopener" target="_blank">#rss</a> <a href="https://mas.to/tags/smolweb" class="mention hashtag" rel="nofollow noopener" target="_blank">#smolweb</a> <a href="https://mas.to/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a>

genehackA couple weeks ago, I added some stuff to my <a href="https://dementedandsadbut.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> config to multiplex SSH and TLS on port 443. Turns out, this FUBARs the downstream TLS logging pretty badly. Anybody have a working config for this use case? <a href="https://dementedandsadbut.social/tags/lazyWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#lazyWeb</a>

Betmig🚀 New video just dropped!In Part 2 of my self-hosted web app series, I show you how to:✔️ Install Docker on a VPS✔️ Set up NGINX Proxy Manager✔️ Auto-deploy with GitHub Actions✔️ Serve your site with HTTPS using Let's EncryptIt’s all running on a hardened Ubuntu server from Hetzner 🛡️📺 Watch it here → <a href="https://youtu.be/NHzT88413Q8" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/NHzT88413Q8</a><a href="https://mastodon.social/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://mastodon.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://mastodon.social/tags/IndieDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#IndieDev</a> <a href="https://mastodon.social/tags/CI_CD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CI_CD</a> <a href="https://mastodon.social/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/BetmigBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#BetmigBuilds</a>

Dan LangilleI want Anubis to be used only for /search.php (and maybe /commit.php) - and I can't figure out how to do that. <a href="https://bsd.network/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> help please

Jan Wildeboer 😷:krulorange:UPDATE: Thx to the replies, I implemented the change for all my domains, did a `certbot renew --dry-run` and that succeeded. Yay to a cleaner config :)<a href="https://social.wildeboer.net/tags/NerdQuestion" class="mention hashtag" rel="nofollow noopener" target="_blank">#NerdQuestion</a>. When I move {server [...] } blocks in `/etc/nginx/nginx.conf` to separate files in the `/etc/nginx/conf.d` directory, will certbot still find them and will automatic renewals just keep working as before? Anyone with experience on that?<a href="https://social.wildeboer.net/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://social.wildeboer.net/tags/letsencrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#letsencrypt</a> <a href="https://social.wildeboer.net/tags/LazyWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#LazyWeb</a>

Deni Mintsaev 🇪🇺502 Bad Gateway <a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a>

Daniel DetlafHave been thinking about <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> and how much I hate Google and <a href="https://mastodon.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener" target="_blank">#WordPress</a> . I've put together a "CMS" that is basically a couple template files that will use server side includes, and some grep/sed aliases for editing them. I skipped most of the history of web development from about 1999 to 2022 ... can anyone wise in the ways of <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> and <a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> tell me if there are any pressing security or other reasons I should not take this approach nowadays? For a static site.<a href="https://mastodon.social/tags/smallweb" class="mention hashtag" rel="nofollow noopener" target="_blank">#smallweb</a>

eklemWhat's the simplest <a href="https://social.vivaldi.net/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#server</a> that can take a fetch() post statement (uploading a blob) from a static <a href="https://social.vivaldi.net/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> in the browser?Something <a href="https://social.vivaldi.net/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> or OneDrive, Google Drive, JottaCloud or something else?

Volker StolzThe good thing about <a href="https://mastodon.social/tags/Nephentes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nephentes</a> is that it ups my <a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> -game.I have to admit I never properly digested the docs, but DID YOU KNOW that `proxy_pass` changes behaviour when using variables!Nice article here by <a href="https://mastodon.social/@dalbuschat" class="u-url mention" rel="nofollow noopener" target="_blank">@dalbuschat</a> that helped me redirect even more useless bots that hit 404s repeatedly into the AI maze vialocation ~ .. { set $upstream http://localhost:port; set proxy_pass $upstream/ai/; }<a href="https://dev.to/danielkun/nginx-everything-about-proxypass-2ona" rel="nofollow noopener" translate="no" target="_blank">https://dev.to/danielkun/nginx-everything-about-proxypass-2ona</a>

stuck.mediaOur shop relies on <a href="https://kolektiva.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> for almost everything:<a href="https://kolektiva.social/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://kolektiva.social/tags/GNULinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNULinux</a> is our operating system.<a href="https://kolektiva.social/tags/inkscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#inkscape</a>, <a href="https://kolektiva.social/tags/gimp" class="mention hashtag" rel="nofollow noopener" target="_blank">#gimp</a>, <a href="https://kolektiva.social/tags/krita" class="mention hashtag" rel="nofollow noopener" target="_blank">#krita</a>, <a href="https://kolektiva.social/tags/imageMagick" class="mention hashtag" rel="nofollow noopener" target="_blank">#imageMagick</a>, <a href="https://kolektiva.social/tags/darkTable" class="mention hashtag" rel="nofollow noopener" target="_blank">#darkTable</a>, <a href="https://kolektiva.social/tags/scribus" class="mention hashtag" rel="nofollow noopener" target="_blank">#scribus</a> are our tools.Our website is handwritten HTML/CSS running on an on-prem server with <a href="https://kolektiva.social/tags/hugo" class="mention hashtag" rel="nofollow noopener" target="_blank">#hugo</a> and <a href="https://kolektiva.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> (launching in June).We contribute to the <a href="https://kolektiva.social/tags/eff" class="mention hashtag" rel="nofollow noopener" target="_blank">#eff</a> and <a href="https://kolektiva.social/tags/wikicommons" class="mention hashtag" rel="nofollow noopener" target="_blank">#wikicommons</a>. To the developers, contributors and maintainers, we salute you!

Jorijn SchrijvershofI'm really surprised that a well-developed product like <a href="https://toot.community/tags/Varnish" class="mention hashtag" rel="nofollow noopener" target="_blank">#Varnish</a> doesn't support connecting to its upstream using TLS. There are quite a few workarounds, but it just seems a bit odd. I'm exploring the idea of serving the contents of an S3 bucket while maintaining a short-lived cache. It shouldn't be too challenging, right?I might just fall back to <a href="https://toot.community/tags/NGINX" class="mention hashtag" rel="nofollow noopener" target="_blank">#NGINX</a>.

Recent searches

Search options

Administered by:

Server stats:

#nginx