Social 📸 Photography

6 posts5 participants0 posts today

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/Freenginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freenginx</a> 1.27.6 has been released (<a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> / <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http</a> / <a href="https://mastodon.social/tags/http2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http2</a> / <a href="https://mastodon.social/tags/http3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http3</a> / <a href="https://mastodon.social/tags/httpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#httpd</a> / <a href="https://mastodon.social/tags/Web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web</a> / <a href="https://mastodon.social/tags/Webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webserver</a> / <a href="https://mastodon.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS</a> / <a href="https://mastodon.social/tags/TLS13" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS13</a>) <a href="https://freenginx.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://freenginx.org/</a>

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> 1.27.5 (dev) has been released (<a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http</a> / <a href="https://mastodon.social/tags/http2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http2</a> / <a href="https://mastodon.social/tags/http3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http3</a> / <a href="https://mastodon.social/tags/httpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#httpd</a> / <a href="https://mastodon.social/tags/Web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web</a> / <a href="https://mastodon.social/tags/Webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webserver</a> / <a href="https://mastodon.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS</a> / <a href="https://mastodon.social/tags/TLS13" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLS13</a>) <a href="https://nginx.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nginx.org/</a>

Jessie (they/she) 🍓 🏳️‍⚧️ 🍉GRRRR!!!I just spent the last hour of my life chasing round in circles just because <a href="https://mstdn.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> wouldnt serve up my css file for some reason. I forced the mime types in the nginx config and everything...Weirdly, Chrome was fine but firefox wasnt when loading this?Anyway, turns out the reason why is because nginx has this *14 year old* bug that means it falls apart whenever there's a dash in a file name. Wtf?! How has no one looked at that yet 😫

Jan ☕🎼🎹☁️🏋️‍♂️Ive built a setup for hosting websites which consists of: * Host running <a href="https://fedi.kcore.org/tags/microos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#microos</a> with <a href="https://fedi.kcore.org/tags/podman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#podman</a> * <a href="https://fedi.kcore.org/tags/Treafik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Treafik</a> and <a href="https://fedi.kcore.org/tags/sshpiper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshpiper</a> at the edge * <a href="https://fedi.kcore.org/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a>, php-fpm, <a href="https://fedi.kcore.org/tags/mariadb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mariadb</a> + phpmyadmin + nginx or <a href="https://fedi.kcore.org/tags/postgres" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postgres</a> + dbadmin, openssh for each siteIt actually works quite well, openssh keybased access is to transfer files into the containers, traefik does the reverse proxying.I'm just wondering if its a sustainable and maintainable setup. Sometimes just going with a "standard" solution seems so much easier.

seungjinFirst switched from <a href="https://mstd.seungjin.net/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a> to Ferron(<a href="https://mstd.seungjin.net/tags/ferronweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ferronweb</a>) on one of my personal servers.

jexnerWhen you self-host immich behind an nginx reverse proxy, be aware that the nginx default configuration blocks uploads of big files!I fell into that trap!<a href="https://discussion.scottibyte.com/t/immich-how-to-bust-the-upload-limits/475" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://discussion.scottibyte.com/t/immich-how-to-bust-the-upload-limits/475</a><a href="https://tooting.ch/tags/immich" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#immich</a> <a href="https://tooting.ch/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

Artanux - Simon LefortMon serveur <a href="https://framapiaf.org/tags/yunohost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#yunohost</a> est à nouveau opérationnel.Cependant, j'ai l'impression de ne pas avoir trouvé la racine du problème. J'ai pu déterminer que Nginx était en cause (il est devenu lent à démarrer alors il timeout et ça a causé les problèmes de mises à jours des applications).J'ai résolu en augmentant le temps avant qu'il timeout. Mais ça me semble un contournement du problème...Il y a des spécialistes en <a href="https://framapiaf.org/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> dans le coin ? J'ai décris le problème là : <a href="https://forum.yunohost.org/t/applications-qui-se-desinstallent-parce-que-la-mise-a-jour-bloque-nginx-qui-ne-demarre-plus/36447/27" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://forum.yunohost.org/t/applications-qui-se-desinstallent-parce-que-la-mise-a-jour-bloque-nginx-qui-ne-demarre-plus/36447/27</a>

Bob<a href="https://mastodon.acc.sunet.se/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> <a href="https://mastodon.acc.sunet.se/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> has a `random_index` directive. Pointing this at a folder with images can be used in static websites to get random background images (or similar shenanigans).<a href="https://mastodon.acc.sunet.se/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://mastodon.acc.sunet.se/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a>

MelLinux 👩‍💻Gibt es jemanden oder mehrere die <a href="https://mastodontech.de/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> als Reverse Proxy UND Webserver unter Docker laufen lassen? Hab es heute einen Tag lang versucht und nicht hinbekommen... Kein Plan warum es nicht funktionieren will.

Felix Palmen :freebsd: :c64:<a href="https://mastodon.bsd.cafe/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Documentation</a> ... better start early I guess. What would you think of this sample <a href="https://mastodon.bsd.cafe/tags/configuration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#configuration</a> file?Hint: the tokens surrounded by %% will be replaced by my build system before installing this thing.For context, this is a web <a href="https://mastodon.bsd.cafe/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authentication</a> service offering cookie+forms login meant for e.g. <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>' "auth_request".<a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Felix Palmen :freebsd: :c64:DId lots of smaller improvements to <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> ... but first, I had to hunt down a crash 🤯. Finally found it was caused by my <a href="https://mastodon.bsd.cafe/tags/poser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poser</a> lib (to be fixed later): A connection there can resolve the hostname of a remote end and does so in a thread job to avoid blocking. If the connection dies meanwhile, the job is canceled. Seems my canceling mechanism relying on a signal to the thread is, well, not reliable (the signal can arrive delayed). Ok, for now just disabled name resolution to sidestep that.Now, integration with <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> is much better. I intrdoduced (optional) custom headers to transport the authentication realm and the redirect URI, plus state management in the session, so these can be passed to the "auth" endpoint. This requires to make sure nginx always passes the session <a href="https://mastodon.bsd.cafe/tags/cookie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cookie</a>, Unfortunately, I still need a "hacky" redirect configuration for login in nginx. If auth_request could just pass the response body, this would be unnecessary .... 🙄 The nginx configuration shows <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> running on "files" and another nginx running on "wwwint" serving <a href="https://mastodon.bsd.cafe/tags/poudriere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poudriere</a> output there. This nginx instance helpfully adds cache hints, which I have to override, so a redirect works as expected when for example the swad session times out.<a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Martin Owens :inkscape:I've set up my new <a href="https://floss.social/tags/inkscape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#inkscape</a> website AI bot trap. It works by giving everyone a chance to not fall into it.An anchor link that says "I am a bot" and links to /P3W-451/{datetime}/ it's got a fixed position at top -100px so should never be seenThe robots.txt says "Disallow: /P3W-451/" so if you were reading the robots, you'd know.Then <a href="https://floss.social/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> logs the requests to a log of their ip-addresses and browser strings and sends them a 301 redirect to google.com<a href="https://floss.social/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://floss.social/tags/Scraping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scraping</a> 1/2

Felix Palmen :freebsd: :c64:First "production test" successful 💪 ... after band-aid "deployment" (IOW, scp binaries to the prod jail).<a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> integrates with <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> exactly as I planned it. And <a href="https://mastodon.bsd.cafe/tags/PAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PAM</a> authentication using a child process running as root also just works (while the main process dropped privileges). 🥳 So, I guess I can say goodbye to <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/bots" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bots</a> hammering my poor DSL connection just to download poudriere build logs.Still a lot to do for <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a>: Make it nicer. So many ideas. Best start would probably be to implement more credentials checking modules besides PAM.<a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Xavier «X» Santolaria :verified_paw: :donor:📨 Latest issue of my curated <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> and <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> list of resources for week #13/2025 is out!It includes the following and much more:➝ DNA of 15 Million People for Sale in <a href="https://infosec.exchange/tags/23andMe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#23andMe</a> Bankruptcy,➝ <a href="https://infosec.exchange/tags/Trump" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trump</a> administration accidentally texted a journalist its war plans,➝ Critical Ingress <a href="https://infosec.exchange/tags/NGINX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGINX</a> controller vulnerability allows RCE without authentication,➝ <a href="https://infosec.exchange/tags/Cyberattack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cyberattack</a> hits Ukraine's state railway,➝ Troy Hunt's Mailchimp account was successfully phished,➝ <a href="https://infosec.exchange/tags/OpenAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenAI</a> Offering $100K Bounties for Critical <a href="https://infosec.exchange/tags/Vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vulnerabilities</a>,➝ <a href="https://infosec.exchange/tags/Meta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meta</a> AI is now available in <a href="https://infosec.exchange/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a> for users in 41 European countries... and cannot be turned offSubscribe to the <a href="https://infosec.exchange/tags/infosecMASHUP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosecMASHUP</a> newsletter to have it piping hot in your inbox every week-end ⬇️<a href="https://infosec-mashup.santolaria.net/p/infosec-mashup-13-2025" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://infosec-mashup.santolaria.net/p/infosec-mashup-13-2025</a>

Felix Palmen :freebsd: :c64:Trying to come up with my own little self-hosted <a href="https://mastodon.bsd.cafe/tags/http" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http</a> <a href="https://mastodon.bsd.cafe/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authentication</a> <a href="https://mastodon.bsd.cafe/tags/daemon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#daemon</a> to work with <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>' "authentication request" facility ... first step done! 🥳Now I have a subset of HTTP 1.x implemented in <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a>, together with a dummy handler showing nothing but a static hello-world root document.I know it's kind of stubborn doing that in C, but hey, <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> it is great fun 🙈 <a href="https://github.com/Zirias/swad" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Zirias/swad</a>

Felix Palmen :freebsd: :c64:<a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bagder</a> Wow. For a few months, I was wondering why I suddenly have bandwidth issues when activating my camera in MS Teams meetings, so others can't understand me any more.A look into my <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> logs seems to clarify. Bots are eagerly fetching my (partially pretty large) <a href="https://mastodon.bsd.cafe/tags/poudriere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poudriere</a> build logs. 🧐 (<a href="https://mastodon.bsd.cafe/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> "watching shit scroll by"?)I see GPTBot at least occassionally requests robots.txt, which I don't have so far. Other bots don't seem to be interested. Especially PetalBot is hammering my server. And there are others (bytedance, google, ...)Now what? Robots.txt would actually *help* well-behaved bots here (I assume build logs aren't valuable for anything). The most pragmatic thing here would be to add some http basic auth in the reverse proxy for all poudriere stuff. It's currently only public because there's no reason to keep it private....Have to admit I feel inclined to try one of the tarpitting/poisoning approaches, too. 😏

SaustrupAfter a lot of tinkering, we finally made it to the latest release of the <a href="https://mstdn.dk/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> ingress controller on the <a href="https://mstdn.dk" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://mstdn.dk</a> cluster. The latest release addresses no less than FOUR <a href="https://mstdn.dk/tags/CVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CVE</a> records. Critical configuration areas had changed, the GeoIP database had to be cached to avoid rate limiting and the <a href="https://mstdn.dk/tags/LUA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LUA</a> engine needed some tweaks before it could handle the relative large number of TLS certificates we're using in the cluster, but we finally made it. Sorry about the hick-ups. We're trying to keep expenses from going through the roof, so we've skipped the test setup in favor of gently tweaking things in production. Usually that goes well, but there is the rare exception.Somewhat related, the <a href="https://mstdn.dk/tags/KubeCon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KubeCon</a> / <a href="https://mstdn.dk/tags/KubeConEU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KubeConEU</a> <a href="https://mstdn.dk/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a> conference is next week, which means I'll be in <a href="https://mstdn.dk/tags/London" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#London</a> for the first time for an entire week. Any suggestions for things worth visiting for a bunch of <a href="https://mstdn.dk/tags/nerds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nerds</a>? :D

steve mookie kongJust discovered this open source tool screeenly that takes screenshots of webpages. (Found it when I was looking at what bots were hitting my site via my nginx logs).<a href="http://screeenly.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://screeenly.com/</a><a href="https://chow.fan/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://chow.fan/tags/tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tools</a> <a href="https://chow.fan/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#web</a> <a href="https://chow.fan/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a>

Marcus NobleIf you're running ingress-nginx in your Kubernetes cluster please take a look at this latest CVE details, it's a big one! Patches are out so please get updating as soon as you can!<a href="https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/</a><a href="https://k8s.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a> <a href="https://k8s.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nginx</a> <a href="https://k8s.social/tags/Ingress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ingress</a> <a href="https://k8s.social/tags/CloudNative" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudNative</a>

Marianne SpillerLet's assume you have messed up your log_format in <a href="https://konfigurationsmanufaktur.de/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> and now want to correct the resulting access.log so that it corresponds to a “log_format combined” - how would you do that? Asking for a friend, of course.

Recent searches

Search options

Administered by:

Server stats:

#nginx