Mastodon

Dusty<a href="https://mstdn.chrisalemany.ca/@chris" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chris</a> I used to use that <a href="https://autistics.life/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> rtmp module myself, in <a href="https://autistics.life/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a>. I now use <a href="https://autistics.life/tags/Owncast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Owncast</a> instead - recommended.

:trone: Shalien... <a href="https://mastodon.projetretro.io/tags/certbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#certbot</a> can't figure how to manage hand compiled <a href="https://mastodon.projetretro.io/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>... like great work there . I would like to NOT have to choose between having zstd / brotli support and automatic tls

mazedlxSo, I’ve just replaced <a href="https://wien.rocks/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> with <a href="https://wien.rocks/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> thanks to <a href="https://phpc.social/@theseer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@theseer</a> for the talk/workshop at <a href="https://wien.rocks/tags/ipc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipc</a> <a href="https://wien.rocks/tags/phpconference" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#phpconference</a> Added bonus: the config file is 10 lines long and is for two hosts, one acting as a reverse proxy. This is brilliant.

BatcastleWorking on moving my <a href="https://mastodon.xyz/@nextcloud" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nextcloud</a> off of <a href="https://linuxrocks.online/tags/Linode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linode</a> and over to self-hosting. I was able to clone the drive over the internet, then flash the image to a drive along with making a swap partition and EFI partition. It boots, and connects to the internet, now to get it to play nicely with my <a href="https://linuxrocks.online/tags/NGINX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGINX</a> reverse proxy. It's in a <a href="https://cloud-native.social/@Docker" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Docker</a> container so this is going to be interesting.

Problem FoxMy <a class="hashtag" href="https://corteximplant.net/tag/smolweb" rel="nofollow noopener noreferrer" target="_blank">#smolweb</a> <a class="hashtag" href="https://corteximplant.net/tag/selfhost" rel="nofollow noopener noreferrer" target="_blank">#selfhost</a> websites are down again but <a class="hashtag" href="https://corteximplant.net/tag/geminiprotocol" rel="nofollow noopener noreferrer" target="_blank">#geminiProtocol</a> is being served as usual. An <a class="hashtag" href="https://corteximplant.net/tag/nginx" rel="nofollow noopener noreferrer" target="_blank">#NGINX</a> IP block list for the IP ranges I'd noted earlier worked for about a minute, long enough for me to watch the light on the WiFi dongle slow to a normal "just me connected" pulse. Then it started again, netstat showed two new ranges. I blocked those and watched the cycle repeat again. Different ranges of addresses every time but always resolving to Brazil so I'm assuming the same controlling source which is almost certainly not in Brazil. I don't want to region block as that seems extreme and inefficient but I'll keep it as a backup option if I can't make a cookie solution like <a class="u-url mention" href="https://social.pollux.casa/@adele" rel="nofollow noopener noreferrer" target="_blank">@adele</a> suggested work.

Deekshith Allamaneni<a href="https://chaos.social/@kubikpixel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kubikpixel</a> I wonder how it compares to Caddy. They mentioned <a href="https://techhub.social/tags/Apache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apache</a>, <a href="https://techhub.social/tags/NGINX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGINX</a> on their website but not <a href="https://techhub.social/tags/Caddy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Caddy</a>.

ShnizmuffiN<a href="https://front-end.social/@kizu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kizu</a> If I had to start my self-hosting journey over again, I'd start with the piece of technology that's responsible for accessing every other piece of technology: the reverse proxy.I chose nginx. I wrote my configs by hand for every subdomain. Then, I discovered all of these:<a href="https://selfh.st/apps/?tag=Reverse+Proxy" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://selfh.st/apps/?tag=Reverse+Proxy</a>It's been eight years. You're never going to refactor your reverse proxy. Make a good first choice!<a href="https://toots.inbutts.lol/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://toots.inbutts.lol/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

Shoe Bill :yellowShield: :yellowHat: :yellowSparkles: :yellowFivePlus: :yellowCrown:Thinking about setting up an Onion site to mirror this domain.I'm running everything through Nginx first, and then having Cloudflare Tunnel talk to Nginx ("everything," at the moment, is just this subdomain, although I just have the other one commented out for now… anyway).So, do I just set up my torrc to serve the Onion site from the same port Cloudflare Tunnel talks to, and give Nginx both server names (for the clearnet site and the Onion site respectively), or…?Also, is there anything else I need to know, or anything that might improve performance and/or security, or whatever?EDIT: oh, and do I need the SSL certificate for the Onion site in order for it to federate properly, or is the one I already have on the clearnet site enough? Asking because, if not, I won't even bother and I'll just serve the Onion site on port 80 and do http only. Thanks.<a href="https://ultracrepidarian.mysteriar.ch/tags/tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a> <a href="https://ultracrepidarian.mysteriar.ch/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a> <a href="https://ultracrepidarian.mysteriar.ch/tags/cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a> <a href="https://ultracrepidarian.mysteriar.ch/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosted</a> <a href="https://ultracrepidarian.mysteriar.ch/tags/askfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AskFedi</a> <a href="https://ultracrepidarian.mysteriar.ch/tags/fedihelp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediHelp</a>

zolarisA <a href="https://mastodon.illumos.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> application runs inside an LX-branded zone, where the <a href="https://mastodon.illumos.cafe/tags/Illumos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Illumos</a> kernel (descended from <a href="https://mastodon.illumos.cafe/tags/Solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solaris</a>) natively implements the Linux kernel ABI. A <a href="https://mastodon.illumos.cafe/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> connection, terminated in a separate Solaris-style zone, routes the application's traffic to a VPN endpoint on an <a href="https://mastodon.illumos.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> system running <a href="https://mastodon.illumos.cafe/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a>, which serves <a href="https://mastodon.illumos.cafe/tags/HTTPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTPS</a> content on a custom domain. Life is great!

BaaWord on the grapevine is NGINX source-code leaked :btr_ikuyo_panic: <a href="https://mk.absturztau.be/tags/nginx" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

PloneVitaliy Podoba shows Integrating Plone and Django: A Real-World Case Study with Nginx SSI<a href="https://2025.ploneconf.org/schedule/talks/integrating-plone-and-django-a-real-world-case-study-with-nginx-ssi" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://2025.ploneconf.org/schedule/talks/integrating-plone-and-django-a-real-world-case-study-with-nginx-ssi</a><a href="https://plone.social/tags/PloneConf2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PloneConf2025</a> <a href="https://plone.social/tags/CMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CMS</a> <a href="https://plone.social/tags/Plone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Plone</a> <a href="https://plone.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://plone.social/tags/Volto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Volto</a> <a href="https://plone.social/tags/ReactJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReactJS</a> <a href="https://plone.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://plone.social/tags/Django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Django</a> <a href="https://plone.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a> <a href="https://plone.social/tags/SSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSI</a> <a href="https://plone.social/tags/CaseStudy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaseStudy</a>

Joel Carnat ♑ 🤪I have discovered a simple way to host a <code>What's My IP</code>-like service with just a little of <a href="https://gts.tumfatig.net/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> and <a href="https://gts.tumfatig.net/tags/geolite2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GeoLite2</a>. Should you want to do it yourself, here are the notes: <a href="https://www.tumfatig.net/2025/check-your-ip-infos-using-nginx/" rel="nofollow noopener noreferrer" target="_blank">https://www.tumfatig.net/2025/check-your-ip-infos-using-nginx/</a>If you're not into hosting it yourself, I have also made it available on <a href="https://ip.nogoo.me" rel="nofollow noopener noreferrer" target="_blank">https://ip.nogoo.me</a>, of course running on <a href="https://gts.tumfatig.net/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>.<a href="https://gts.tumfatig.net/tags/runbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunBSD</a>

/dev/loop0I feel defeated, I was not able to make <a href="https://freeradical.zone/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> running under docker to get the request real ip. It seems like <a href="https://freeradical.zone/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#docker</a> userland-proxy just fucks it up.

release_candidateIs there a way to have nginx calling blocklistd in NetBSD?Like, when it returns 444 or 403 statuses?<a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://mastodon.bsd.cafe/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a>

Torger Åge Sinnes<a href="https://snabelen.no/tags/Vevtenar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vevtenar</a> på <a href="https://snabelen.no/tags/solceller" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solceller</a>. 🤘🎉 Ikkje så avansert som <a href="https://solar.lowtechmagazine.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://solar.lowtechmagazine.com/</a>, men heilt greit proof of concept. Lærte og å sette opp <a href="https://snabelen.no/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> til å levera fleire nettstader. Ikkje så vanskeleg. Alt ein får gjort.... 🤓 <a href="https://snabelen.no/tags/justbecauseican" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#justbecauseican</a>

Olivier MehaniEnabling HTTP/3 and QUIC in nginx<a href="https://blog.narf.ssji.net/2025/10/10/enabling-http-3-and-quic-in-nginx/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.narf.ssji.net/2025/10/10/enabling-http-3-and-quic-in-nginx/</a>Enabling HTTP/3 and QUIC in nginx is relatively straight forwards, and well documented. This was also an opportunity to update my basic configuration.tl;dr:* `http3 on` and `listen [::]:443 quic reuseport default_server` need to be added.* QUIC is over UDP, so the port needs to be opened in the firewall.* User-agents need to be told that it is now available., e.g., with an `add_header Alt-Svc ‘h3=”:443″; ma=86400’`.* HTTP/3 requires `ssl_protocols TLSv1.3`.<a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://blog.narf.ssji.net/tag/curl/" target="_blank">#cURL</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://blog.narf.ssji.net/tag/http3/" target="_blank">#http3</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://blog.narf.ssji.net/tag/nginx/" target="_blank">#nginx</a>

Thoralf Will 🇺🇦🇮🇱🇹🇼Der <a href="https://soc.umrath.net/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> proxy manager (npm) hat ein cooles Interface und ist leicht zu bedienen - hat dafür aber eklige Einschränkungen (z.B. nur ein Port pro URL).traefik kann echt alles, hat aber kein intuitiv zu bedienendes Interface.Dilemma.

HadiFinally managed to finish rewriting my <a href="https://fosstodon.org/tags/website" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#website</a> with a very lean <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> script that exports <a href="https://fosstodon.org/tags/org" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#org</a>-mode files to HTML and serves using <a href="https://fosstodon.org/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>. It needs some polishing down the road, but it does the job a rather heavy <a href="https://fosstodon.org/tags/FastAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FastAPI</a> app used to do.<a href="https://hadi.timachi.com/posts/new_website_pandoc_python_nginx" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hadi.timachi.com/posts/new_website_pandoc_python_nginx</a>

Nico -telmich- SchotteliusCreated a bug report to request <a href="https://ipv6.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>-ingress to move away from <a href="https://ipv6.social/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> - see my previous toot for details. <a href="https://github.com/kubernetes/ingress-nginx/issues/14009" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kubernetes/ingress-nginx/issues/14009</a>

Fabio ManganielloBest <a class="hashtag" href="https://manganiello.social/tag/nginx" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> hack to get rid of most of Google’s bots from your website:<pre><code>map $http_user_agent $block_user_agent { default 0; # do not block by default ~*"(Nexus 5X)"* 1; } server { if ($block_user_agent) { return 403; } }</code></pre>Don’t worry, nobody uses a Nexus 5X anymore.For some reason in the past 1-2 years Google bots have stopped abiding to the gentlemen’s convention of using the<code>+http://www.google.com/bot.html</code> string somewhere in their UA and they just dump you user agents like this where they pretend to be a 10-year-old Android device:<pre><code>Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.7258.127 Mobile Safari/537.36 (compatible; GoogleOther)</code></pre>And, since apparently in some cases they also stopped abiding to the gentlemen’s agreement of respecting the <code>robots.txt</code>, this is probably a more explicit way of keeping them at bay.

Recent searches

Search options

Administered by:

Server stats:

#nginx