Med-Mastodon

9 posts9 participants0 posts today

RyeLooking for some help troubleshooting django and gunicorn - images are not rendering in production <a href="https://ioc.exchange/tags/django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#django</a> <a href="https://ioc.exchange/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://ioc.exchange/tags/gunicorn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gunicorn</a> <a href="https://ioc.exchange/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

thezerobitThinking about firing up a <a href="https://anticapitalist.party/tags/VPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPS</a> to run my own software (wiki, <a href="https://anticapitalist.party/tags/gotosocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gotosocial</a>, ???). I want something cheap and lightweight, so I'll probably just manage the server myself. It's been like 10 years since I've done this. Before, I've just run Ubuntu Server, which worked well at the time. I think I used <a href="https://anticapitalist.party/tags/supervisord" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#supervisord</a> to manage services, IIRC, with <a href="https://anticapitalist.party/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> as the public gateway w/ manual routing configs. Not sure what is best for this type of hosting now. I want to avoid docker images for efficiency sake.

Ryan PetersSet up a script to ping me when my fail2ban blocks a malicious IP (and grabs the location) trying to connect to my <a href="https://social.binarydad.com/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> reverse proxy. I swear at some point I'll block every IPv4 out there.

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 noreferrer" target="_blank">#webdev</a> <a href="https://toot.cafe/tags/svelte" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#svelte</a> <a href="https://toot.cafe/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a> <a href="https://toot.cafe/tags/css" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#css</a> <a href="https://toot.cafe/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a> <a href="https://toot.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://toot.cafe/tags/lua" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lua</a> <a href="https://toot.cafe/tags/freelancer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freelancer</a>

Tom :damnified:Seit einigen Tagen werden Medien meiner Mastodon-Instanz metalhead.club global verteilt über ein eigenes CDN ausgeliefert. :goose_hacker: Das verringert die Latenzen für Benutzer aus nicht-EU Ländern und sorgt für weniger Frust bei den Ladezeiten. Was ein CDN ist, welche Implementierungsmethoden es gibt und wie ich mein kleines CDN umgesetzt habe, erfahrt ihr in meinem neuen Blogpost: "Ein eigenes kleines CDN für meine Mastodon-Instanz metalhead.club" - <a href="https://thomas-leister.de/mastodon-media-storage-cdn/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thomas-leister.de/mastodon-media-storage-cdn/</a><a href="https://metalhead.club/tags/metalheadclub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#metalheadclub</a> <a href="https://metalhead.club/tags/cdn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cdn</a> <a href="https://metalhead.club/tags/media" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#media</a> <a href="https://metalhead.club/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a> <a href="https://metalhead.club/tags/instance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#instance</a> <a href="https://metalhead.club/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastoadmin</a> <a href="https://metalhead.club/tags/hosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hosting</a> <a href="https://metalhead.club/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://metalhead.club/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://metalhead.club/tags/scaleway" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scaleway</a> <a href="https://metalhead.club/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dns</a> <a href="https://metalhead.club/tags/geoip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geoip</a> <a href="https://metalhead.club/tags/geodns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geodns</a> <a href="https://metalhead.club/tags/hetzner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hetzner</a>

CeceliaI just launched a new phpBB forum. The rollout was super smooth despite my doing it via git deployment. I feel like I’ve reached a comfortable level with my Nginx configuration skill.The hardest part was setting up Postfix with Domain Keys and Sender Policy Framework correctly.<a href="https://tech.lgbt/tags/phpBB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#phpBB</a> <a href="https://tech.lgbt/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a>

Jesse SkinnerI've said this before, but I can't say it enough: OpenResty (nginx+lua) is painfully underappreciated. It's fantastic, and the only platform I trust for very high volume, high performance, mission critical web application servers.<a href="https://toot.cafe/tags/openresty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openresty</a> <a href="https://toot.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://toot.cafe/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webdev</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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#nginx</a>. <a href="https://mas.to/tags/rss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rss</a> <a href="https://mas.to/tags/smolweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#smolweb</a> <a href="https://mas.to/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a>

ct 3003Homeserver von außen erreichbar machen! <a href="https://peertube.heise.de/w/5kEnVvFHevZBwTBA8L3Vxn" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://peertube.heise.de/w/5kEnVvFHevZBwTBA8L3Vxn</a>

Jan ☕🎼🎹☁️🏋️‍♂️Testing out <a href="https://fedi.kcore.org/tags/tebi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tebi</a> object storage with <a href="https://fedi.kcore.org/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> caching in front of it instead of <a href="https://fedi.kcore.org/tags/backblaze" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backblaze</a> <a href="https://fedi.kcore.org/tags/b2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#b2</a> with <a href="https://fedi.kcore.org/tags/cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudflare</a>.

genehackA couple weeks ago, I added some stuff to my <a href="https://dementedandsadbut.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#lazyWeb</a>

Felix Palmen :freebsd: :c64:<a href="https://mendeddrum.org/@fanf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fanf</a> Sure that does make sense. I'll try to verify jmeter indeed doesn't reuse connections (I already have debug logging in place that should tell me).If that's really the reason, I guess the sane thing to do is to add a hint to the docs to just disable TLS for very busy sites. The intended usecase for <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> is operation behind <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> to serve its "auth_request". I don't intend to implement HTTP/2 or beyond, but it would be pretty pointless here anyways, nginx defaults to HTTP/1.0 for proxy requests and can be configured to use HTTP/1.1 instead, but *still* doesn't reuse connections by default, and my experiments so far to enable it weren't successful, maybe I didn't fully understand it yet. Using TLS behind nginx would make sense from a "defense in depth" point of view, but it's probably impractical once your load exceeds a certain threshold.For background how I arrived there, I observed stupid <a href="https://mastodon.bsd.cafe/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://mastodon.bsd.cafe/tags/scraper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scraper</a> <a href="https://mastodon.bsd.cafe/tags/bots" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bots</a> clog my DSL connection by downloading gigabytes of build logs produced by my <a href="https://mastodon.bsd.cafe/tags/poudriere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poudriere</a>. They're not secret in any way and having a simple way to share them is great for community bug hunting, but this had to stop. I had a simple C library doing a fully portable reactor event loop on top of select (so, not really scalable), and some very limited HTTP/1.1 server code from experiments with TOR hidden services ... so I put that together to add some web-form + cookies auth to my private nginx to lock out the bots. Later, I added a "guest login" doing the same "proof of work" stuff known from <a href="https://mastodon.bsd.cafe/tags/anubis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#anubis</a>, and then I suddenly had the idea in mind to make my little service (that already solved the problem perfectly for myself) suitable for large-scale installations. So, added kqueue, epoll etc support, added a "multi-reactor with acceptor-connector" design, etc .... and now I'm a bit frustrated enabling TLS spoils all the performance 🙈

SamOk how cool is this? I have one IPv4 address and want to terminate TLS/HTTPS on different machines depending on the hostname.It turns out Nginx can detect the hostname and route the traffic without having the cert/terminating the traffic. Magic!<a href="https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html</a><a href="https://social.running.cafe/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://social.running.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

Jeff Starr✨ 🤖 New version of Ultimate Block List to Stop <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://mastodon.social/tags/Bots" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bots</a>. Version 1.5 features 20+ new bots, improved regex/pattern-matching, and rules formatted for <a href="https://mastodon.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a> ✨ <a href="https://perishablepress.com/ultimate-ai-block-list/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://perishablepress.com/ultimate-ai-block-list/</a>

Gardiner BryantNot sure if you guys noticed but I haven't posted an article to The Bryant Blog since last Saturday. That's because I've been working on this beast.<a href="https://mastodon.online/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://mastodon.online/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://mastodon.online/tags/opnsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opnsense</a> <a href="https://mastodon.online/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proxmox</a> <a href="https://mastodon.online/tags/reverseproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reverseproxy</a> <a href="https://mastodon.online/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://mastodon.xyz/@nextcloud" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nextcloud</a> <a href="https://gardinerbryant.com/opnsense-nginx-reverse-proxy-for-your-homelab/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gardinerbryant.com/opnsense-nginx-reverse-proxy-for-your-homelab/</a>

Elizabeth K. JosephThe <a href="https://floss.social/tags/s390x" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#s390x</a> open source software team at IBM confirms the latest versions of various software packages run well on <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> on <a href="https://floss.social/tags/IBMZ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IBMZ</a> & <a href="https://floss.social/tags/LinuxONE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxONE</a> 🐧 In April 2025 validation was maintained for over 40 projects, including <a href="https://floss.social/tags/Apache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apache</a> Hbase, HashiCorp <a href="https://floss.social/tags/Consul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Consul</a> and <a href="https://floss.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> 🎉 Plus, community CI was added for zaars, V (programming lang), & Exiv2Full report + how your project can apply for a s390x VM: <a href="https://community.ibm.com/community/user/blogs/elizabeth-k-joseph1/2025/05/29/linuxone-open-source-report-april-2025" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://community.ibm.com/community/user/blogs/elizabeth-k-joseph1/2025/05/29/linuxone-open-source-report-april-2025</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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#nginx</a> <a href="https://social.wildeboer.net/tags/letsencrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#letsencrypt</a> <a href="https://social.wildeboer.net/tags/LazyWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LazyWeb</a>

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

Daniel DetlafHave been thinking about <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webdev</a> and how much I hate Google and <a href="https://mastodon.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#http</a> and <a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#smallweb</a>

Recent searches

Search options

Administered by:

Server stats:

#nginx