I’m almost going full circle now, I’m buying a camera and a Music player to use as separate devices from my phone. Not only smartphones are getting expensive as hell, but the usability is actually getting worse IMHO.

And why is it so fucking awful to setup an automated pipeline to deploy smartphone apps (Android and iOS)?

Free Download Manager was pretty rad. Being able to resume the download later was a life saver for dial-up connections. I remember that it took me almost a week to download Gunbound.

I hope “normal people” start exploiting that decision too. Training AI to consume stuff from big corporations and using the result to create open source/copyright free stuff from copyrighted works.

Oh man, I would kill for this…

I don’t know exactly about Woodpecker CI because I haven’t used it very much, but GitHub Actions is Beta software. Has A LOT of bugs, no QoL features, spaghetti codebase, the Runners are AWFUL to selfhost… and I could go on.

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

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

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}
        }
}

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

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

Yeah, I wish Nextcloud focused more on the file manager side of their applications. I was using it on my TrueNAS instance and it seems like an unfinished product. E2EE is not enabled by default and looks like their implementation is not perfect either.