Oooh the irony!

“We should be very careful lest we hurt the feelings of Zionists”

If you want to fight antisemitism, you should be fighting Israel. They’re the largest source of antisemitism worldwide by enacting a genocide in the name of Judaism.

Yeah. And you can pin messages, have pills, edit messages and schedule send.

Zionism is, and has always been since the modern movement started in the 19th century, intrinsically antisemitic.

Hello all,

I figured that a chunk of the selfhost community is using Caddy, so decided to post my query here. I am a novice in Caddy, so I might be saying some incorrect terms.

Some information - The router and the host running Caddy, are different machines - The router page is running HTTP, but I am accessing it via HTTPS through Caddy - Caddy is running via Docker.

I have a couple of services running on a host, so I access them via Caddy’s reverse proxy. Now I am also trying to access my router login via the same reverse proxy. This is what the router entry in the caddyfile looks like

.
.
{
    local_certs
}
login.router.lan {
	reverse_proxy 192.168.1.1:80
}
.
.

With this entry, I can access the login page. However, when I enter the password, I feel like it’s attempting to login but then it just comes back to the original login page. When I access it directly, the login is successful. I also have Pihole running and the Pihole login process works fine. So I suspect that the router login page is expecting some extra information from Caddy to forward it to the login page.

After some searching online and some LLM wrangling, I figured it’s some cookie issue or my login page is expecting a certain host.

What should I add to my Caddyfile so that the login redirect works?

Semi related, you can check the validity of Caddy entries into the caddyfile:

• sudo caddy fmt --overwrite /etc/caddy/Caddyfile
• caddy validate --config /etc/caddy/Caddyfile

Where /etc/caddy/Caddyfile points to your caddyfile.

I have tried this, but unfortunately, it did not work. I have tried this suite of commands

login.router.lan {
    reverse_proxy 192.168.1.1:80 {
        # Preserve original host and scheme
        header_up Host {upstream_hostport}
        header_up X-Forwarded-Proto {http.request.scheme}
        header_up X-Forwarded-Host {http.request.host}
        header_up X-Forwarded-For {http.request.remote.host}

        # Keep cookies intact
        header_up Cookie {http.request.header.Cookie}
        header_down Set-Cookie {http.response.header.Set-Cookie}

        # Preserve Origin/Referer for CSRF tokens
        header_up Origin https://{http.request.host}
        header_up Referer https://{http.request.host}{http.request.uri.path}
    }
}

Info: My caddy uses HTTPS but the router login page is HTTP. Not sure if this is relevant.

All these speeds the providers advertise (especially the faster ones) are often cut down by bad peering. I often had an issue downloading bigger files from my storage when I was traveling. Only got some single digit MBit transfer speeds due to bad peering, while speed tests has shown decent results. When it comes down to Selfhosting the upload/download figures alone not always tell the truth. In my point of view 20Mbps is actually even sufficient for most of private stuff, even streaming HD content to one ore two peers simultaneously.

That whoever is going to be me

Obama medal meme

@pepper0@aus.social @fediverse@piefed.social well, #misskey has a feature called "antenna" to follow statuses by combination of keywords