proton_lynx

proton_lynx , 17 days ago

I'm using BorgBase with Vorta (desktop client for Borg Backup) and I'm pretty happy with it.

proton_lynx , 2 months ago

Oh yes, the good ol' disk destroyer!

proton_lynx , 2 months ago

Save money, buy an Apple computer. Choose one.

proton_lynx , 2 months ago

Holy shit, and this is from 2005/2006. It has only gotten worse.

proton_lynx , 3 months ago

Have you ever checked for hypothyroidism? I was feeling exactly like you described for 2 years. Then, with a blood test, I discovered I had hypothyroidism and started treating it. Feeling a lot better now.

proton_lynx , 4 months ago

You should tell Theo that he will miss her :'(

proton_lynx , 4 months ago

301 Moved Permanently is usually not something that requires user intervention. Most browsers should automatically detect the 301 Moved Permanently response code and redirect automatically.
What happens when you run cURL with the --location flag?

curl --location https://nextcloud.domain.com

proton_lynx , 4 months ago

More than 50 redirects? Hmm, that looks weird.
What is the output when you run wget --spider https://nextcloud.domain.com?
Could you try enabling cookies for cURL and pasting the contents of the cookiefile here?

curl --cookie cookiefile --cookie-jar cookiefile --location https://nextcloud.domain.com

proton_lynx , 4 months ago

Yep, definitely something wrong with the webserver 😅
Can you try this configuration?

https://nextcloud.domain.com {
        reverse_proxy 192.168.1.182:443 {
                header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                header_up X-Forwarded-Proto {scheme}
                header_up X-Forwarded-For {remote}
                header_up X-Real-IP {remote}
        }
}

You said that "originally, the Nextcloud server handled HTTPS with Let’s Encrypt at domain.com" and now you are redirecting to 192.168.1.182 on port 443. Is this Nextcloud server still serving HTTPS with Let’s Encrypt for domain.com?

I'm asking because if you are using Caddy in front of that HTTPS webserver as a reverse-proxy, you will need to override the Host header with the configured upstream address. Here's the documentation.
I think it would be something like this (?):

https://nextcloud.domain.com {
        reverse_proxy domain.com:443 {
                header_up Host {upstream_hostport}
                header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                header_up X-Forwarded-Proto {scheme}
                header_up X-Forwarded-For {remote}
                header_up X-Real-IP {remote}
        }
}

proton_lynx , 4 months ago

Ask your doctor to check your TSH and T3/T4 levels. That's just like a regular blood test.

proton_lynx , 5 months ago

We need more cowbell