nginx

Tags

Follow from the Fediverse

Follow #nginx from Mastodon or any other Fediverse app and its public posts arrive in your timeline. No vutuv account needed.

@nginx@tags.vutuv.de

Your address is used once, to send you to your own server's follow dialog. It is never stored here.

The most endorsed users with this tag

Posts with this tag

17 posts

Filters

⚠️ 📢 Sicherheitswarnung: #NGINX – Mehrere kritische #Schwachstellen bedrohen Webserver

Am 18.11.2026 veröffentlichte F5 Inc. mehrere Advisories zu kritischen Schwachstellen in NGINX Open Source & NGINX Plus. Diese betreffen verschiedene Komponenten & Verarbeitungswege, darunter HTTP/2, HTTP/3, den DNS-Resolver sowie den Mail-Proxy. Sicherheitsforscher fassen fünf NGINX-Schwachstellen unter “NGINX2Root” mit einer weiteren Linux Schwachstelle zusammen.

👉️ bsi.bund.de/dok/…

@certbund@social.bund.de

So yesterday was fun. Summary:

#Drupal vuln mitigated by our default NGINX config.

#NGINX vuln also mitigated by our default config, although we did have to disable http2 on all client #GitLab CE servers.

#Java vuln patched where necessary (a handful of clients run Java, you know who you are).

The #ruby vulns mostly impact #GtiLab, we expect they will make a security release and it will be automatically applied by unattended-upgrades as usual.

Let’s see what #PHP has for us later. 😅

Bianca Kastl @bkastl mastodon.social

Fände übrigens ein Coordinated Vulnerability Release Programm sinnvoll, nicht 2 RCE, die Grundlagentechniken des Internets betreffen, so kurz hintereinander zu releasen.

Ja, updated auch nginx, wenn ihr könnt #nginx #nginx2root nginx2root.com

🫧 Social coding commons @smallcircles social.coop

🚨 URGENT: Self-hosters who use #NGINX reverse proxy should upgrade soonest due to multiple CVE’s that allow remote code execution.

The nginx-1.30.7 stable and nginx-1.31.9 mainline versions contain fixes for these critical vulnerabilities.

A workaround if you can’t update immediately is to disable http2, where that is on in your installation.

wiz.io/blog/…

cve.org/CVERecord?id=CVE-2026-123633

cve.org/CVERecord?id=CVE-2026-123007

news.ycombinator.com/item?id=50547374

Stefano Marinelli @stefano mastodon.bsd.cafe

Me: “Static websites are great for security! No CMS, no database, no PHP, no plugins. Just a few innocent HTML files. What could possibly go wrong?”

nginx: “Hold my CVE.”

Me: “Well, technically, I said the website was secure. I never said anything about the web server.”

And this, kids, is why we can’t have nice things. Not even an index.html.

Stefano Marinelli - littleFedi @stefano littleone.littlefedi.social

littleFedi: reverse proxy and split domains
littleFedi can use one domain for account handles and another for the server. For example:

@alice@example.com is the address people follow.
social.example.com serves the web interface, API, media and ActivityPub objects.

You can keep your existing website on example.com. It only needs a rule that redirects WebFinger requests to the littleFedi domain.

Choose both domains before creating accounts. Changing them later changes the instance’s identity.

littleFedi configuration
In littlefedi.toml, with the reverse proxy running on the same machine:

local_domain = “example.com”
web_domain = “social.example.com”

[http]
listen = “127.0.0.1:8080”
proxy_uri = “social.example.com”
trusted_proxies = [“127.0.0.1/32”]

If you already have an [http] section, edit it rather than adding another.

Point the DNS records for social.example.com at the reverse proxy. The server hosting example.com must also serve HTTPS. A DNS alias alone does not replace the WebFinger redirect.

Expose ports 80 and 443 on the proxy and keep port 8080 private. If the proxy runs on another machine, use a private listener address and trust only the proxy’s address.

Caddy
Add this to your Caddyfile, replacing the example domains:

social.example.com {

reverse_proxy 127.0.0.1:8080

}

example.com {

redir /.well-known/webfinger [social.example.com{uri}](https://social.example.com{uri}) 302

}

Caddy handles certificates and the WebSocket connections used for streaming.

If example.com already has a site block, add only the redir line to that block and keep the existing website configuration.

Check the configuration before reloading Caddy:

caddy validate –config /etc/caddy/Caddyfile

nginx
This configuration belongs in nginx’s http context, usually through an included site file. Replace the domains and certificate paths with your own.

Install valid certificates and arrange automatic renewal before enabling the HTTPS servers.

map $http_upgrade $connection_upgrade {

default upgrade;
'' close;

}

server {

listen 80;
listen [::]:80;
server_name example.com social.example.com;
return 308 [$host$request_uri](https://$host$request_uri);

}

server {

listen 443 ssl;
listen [::]:443 ssl;
server_name social.example.com;

ssl_certificate /etc/letsencrypt/live/social.example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/social.example.com/privkey.pem;
client_max_body_size 41m;

location / {
    proxy_pass [127.0.0.1:8080](http://127.0.0.1:8080);
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_read_timeout 1h;
    proxy_buffering off;
}

}

server {

listen 443 ssl;
listen [::]:443 ssl;
server_name example.com;

ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

location = /.well-known/webfinger {
    return 302 [social.example.com$request_uri](https://social.example.com$request_uri);
}

location / {
    return 404;
}

}

If example.com already hosts a website, add only the WebFinger location to its existing HTTPS server block. Keep the website’s other rules instead of the return 404 shown above. If you already have the same map directive, do not add it twice.

Check the configuration before reloading nginx:

nginx -t

Check discovery
Use an existing local account, replacing alice with its username:

curl –fail -i ‘example.com/.well-known/…

The response should redirect to social.example.com, keeping the resource query parameter.

Then follow the redirect:

curl –fail -L ‘example.com/.well-known/…

The JSON should contain acct: as its subject, with an ActivityPub actor link at social.example.com/users/….

Finally, check a follow in both directions with another instance.

If account handles and the server use the same domain, only the reverse proxy is needed.

littleFedi SelfHosting ReverseProxy nginx caddy

Replying to @deuchnord@social.deuchnord.fr

Souvent les préfixes sont stables, seuls les 56 ou 64 derniers bits changent.

#Nginx
allow 2a01:cb19:xxxx:xxxx::/64; #tu autorise la rotation des 64 bits suivants
deny all;

Mais c’est pas le plus sécurisé qui soit, donc la plupart de mes clients forcent l’IPV4 sur la Préprod, ajoutent un SSO, ou ne permettent l’accès qu’en VPN sur une machine qui, elle, ne change pas d’IP.

1
Flow im Ohr @rene blog.hamdorf.org

Eine Auswertung von einer Woche Logfiles und ein Blick darauf, wohin das „neue“ Internet steuert. Der Anlass Inspiriert von einem Beitrag über das Thema KI-Crawler auf kaffeeringe.de wollte ich wissen wie auf meinen Domains die Lage ist. Ich betreibe auf einem YunoHost-Server bei IONOS mehrere Dienste: dieses Blog, Nextcloud, PeerTube, Funkwhale und ein paar kleinere Anwendungen. Das ist […]

blog.hamdorf.org/ki-crawler-und-das-neu…

Keyboard shortcuts

Navigation

Home g h
Feed g f
Messages g m
Notifications g n
Your profile g p
Search /

Actions

Write a new post n
Send the post or message you are writing ⌘/Ctrl ↵
Next post in the feed j
Previous post in the feed k

General

Show this help ?
Close menus and dialogs Esc

The single-key shortcuts pause while you type, and are off on phones and tablets.