[-] Ooops@feddit.org 3 points 2 hours ago* (last edited 2 hours ago)

Gab diverse Berichte von Besuchern (ich persönlich hab vorallem internationale gesehen), die wegen Regenbogenflaggen, FCKNZ-Patches und ähnlichem nicht aufs Gelände kamen, und das obwohl man drinnen solche Patches natürlich zu kaufen kriegt. Teilweise noch in Kombination mit "aber die Gestalten in Thor Steinar Kluft wurden brav ignoriert und eingelassen" und in krassem Gegensatz zu dem, was das Wacken offiziell zu dem Thema zu sagen hat.

Da gab's also sehr viel Kopfschütteln über die Security und wer auf die Idee gekommen ist, die Typen ausgerechnet da den Einlass regeln zu lassen.

Edit: https://www.fr.de/panorama/patch-abreissen-fuehle-ich-mich-hier-nicht-mehr-sicher-wacken-besucherin-muss-anti-afd-94424737.html

[-] Ooops@feddit.org 11 points 8 hours ago

"Da es während eines solchen Gesprächs nicht immer möglich ist, falsche oder irreführende Behauptungen sofort zu korrigieren,"

... weigern wir uns grundsätzlich auch die offensichtlichsten Falschaussagen sofort zu korrigieren. Denn die Realität könnte das ÖRR Publikum verunsichern, die aber glücklicherweise solche nachträglichen Faktenchecks nie zu Gesicht bekommen.

[-] Ooops@feddit.org 1 points 19 hours ago

That's my point. A version upgrade having issues would have forced you to do it by now.

[-] Ooops@feddit.org 8 points 19 hours ago* (last edited 19 hours ago)

The structure behind rising climate change scepticism in Germany is exactly the same as everywhere else: drowning in brain-numbing amounts of right-wing propaganda screaming 24/7 that opens up about 2-3 new anti-science and counter-factual culture war fronts per day as a diversion.

As the planet heats, public doubt grows

But nice try implying some correlation or even causation here. 🖕

[-] Ooops@feddit.org 5 points 20 hours ago

No, all those tech idiots are actually trying to destroy the world then rule over the ruins from their secure luxury bunkers and islands. Maximized disruption and destructive tendencies backfiring from time to time is just a side effect.

[-] Ooops@feddit.org 9 points 1 day ago

ich meine ich sag ja meine meinung, aber finde mich jetzt nicht sooo kontrovers

Ab genug geisteskranker Verschiebung des Diskurses nach stramm Rechts, sind halt auch gewöhnliche Menschenrechte und Grundideen des Grundgesetzes wieder "kontrovers"... 🫤

[-] Ooops@feddit.org 18 points 1 day ago

Gäbe es tatsächlich Zeichen des Himmels würde ihn wohl eher der Blitz beim Scheißen treffen...

[-] Ooops@feddit.org 10 points 1 day ago

I was too lazy for scripting the update to check the news and just get a mail when the update has issues... or should get one.

In reality I check if the email process still works once every blue moon because I didn't get one from a failed update in years.

[-] Ooops@feddit.org 6 points 1 day ago

Well... because of longer testing periods and a lot of stuff never even considered until stale the stable distros indeed have less bugs. The ones that still slip through however will basically not get fixes for years.

On the other hand I have seen a lot of bugs on Arch... but I usually don't care and just assume (rightfully so in 99% of the cases) that they get fixed within hours.

[-] Ooops@feddit.org 6 points 1 day ago* (last edited 1 day ago)

I wonder how many Arch haters have actually used Arch and ever ran into a breaking issue.

A lot... they install it, screw up because they didn't bother to read the instructions, then did the usual... a new install.

Those who pass the first basic barrier to just chroot into the system and fix a simple mistake or roll back a package for the few hours it takes to get fixed instead of starting fresh usually stay for a long time...

In fact with the people I know there is a correlation between either "oh, I don't bother to fix anything and just do a fresh install (that idea is especially persistent in Windows users)" or "there's a big distro upgrade that had issues" and distro hopping. Once you settled on a rolling release and learned the basics in terms of fixing stuff the urge to hop yet another time vanishes for many.

[-] Ooops@feddit.org 11 points 1 day ago

As everyone knew it would happen once the loud, crying propagandists screamed about deporting criminal Afghans while actually nullifying already existing visa for Afghans that helped the German army for years...

35
submitted 1 month ago by Ooops@feddit.org to c/unixporn@lemmy.world

25
submitted 3 months ago* (last edited 3 months ago) by Ooops@feddit.org to c/selfhosted@lemmy.world

As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

So a (very simplified) nginx server-block that looks like this:

# serve stuff internally (without a hostname) via http
server {
	listen 80 default_server;
	http2 on;
	server_name _; 
	location / {
		proxy_pass http://localhost:5555/;
                \# that's where all actual stuff is located
	}
}
# reroute http traffic with hostname to https
server {
	listen 80;
	http2 on;
	server_name server_a.bla;
	location / {
		return 301 https://$host$request_uri;
	}
}
server {
	listen 443 ssl default_server;
	http2 on;
	server_name server_a.bla;
   	ssl_certificate     A_fullchain.pem;
    	ssl_certificate_key A_privkey.pem;
	location / {
		proxy_pass http://localhost:5555/;
	}
}
#actual content here...
server {
	listen 5555;
	http2 on;
    	root /srv/http;
	location / {
        	index index.html;
   	} 
    	location = /page1 {
		return 301 page1.html;
	}
    	location = /page2 {
		return 301 page2.html;
	}
        #reverse proxy for an example webdav server 
	location /dav/ {
		proxy_pass        http://localhost:6666/;
	}
}

Which works well.

And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

So long story short...

How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?

view more: next ›

Ooops

0 post score
0 comment score
joined 2 years ago