nelson

Huh. Didn’t even know about this. Maybe I’ll browse their episode list to see if there are some episodes that are interesting.

deleted by creator

The issue you linked mentions using pasta where it does work. Have you tried that or is it not a solution at all?

Fair Point! I’m running photoprism myself which is stable, even though the PWA works well, it’d be nice to have a native app that can do the syncing rather than having to buy/rely on a 3rd party tool.

Also - If you’re looking for Auto-Sync features for the photos ( automatic upload when you take the pics ) there isn’t a free option on Android for photoprism ( I think ). There’s photo-sync, which will cost you about 3 euros or something.

If they want to upload pictures manually then there’s no issue.

Immich could be an option ( has an app and user mgmt ).

Photoprism can work too, but that only had a web/PWA version IIRC.

What happens when you directly curl the nextcloud? From a device that can access it, such as the machine where your caddy is running.

curl -v https://192.168.1.182

I am assuming it will reply with a 301 moved and add a location header that points to “https://nextcloud.domain.com”.

It’s looping back to itself? Location header is pointing back to itself.

Is it possible your backend is sending back an http 301 redirect back to caddy, which forwards it to your browser?

Possibly some old configuration on your backend from the letsencrypt beforehand? Can you check the logs from your backend and see what they’re sending back?

I’m assuming the request might replace the host with the IP on your reverse Proxy and that your next cloud backend is replying with a redirect to https://nextcloud.domain.com:443

Edit: I think this is the most incoherent message I wrote to date.

I think your reverse Proxy is forwarding the request to your next cloud, but replacing the Host header with the IP you specified as reverse Proxy. As a result the request arrives at your next cloud with the IP as “host”.

Your next cloud installation is then sending back a 301 redirect to tell the client that they should connect to https://nextcloud.domain.com. this arrives through caddy at your browser, goes through the same loop until you’ve reached the max redirects.

Have a look at your next cloud backend http logs to see what requests are arriving there and what HOST( http header ) it’s trying to connect to on that IP.

anything can output that even PHP.

That sounded pretty bitter.

Good luck! :)

Are you sure about that?

https://coder.com/docs/code-server/latest/install#npm

Below is quoted from the article

We recommend installing with npm when:

You aren’t using a machine with amd64 or arm64. You are installing code-server on Windows. You’re on Linux with glibc < v2.28 or glibcxx < v3.4.21. You’re running Alpine Linux or are using a non-glibc libc. See #1430 for more information.

Installing code-server with npm builds native modules on install.

This process requires C dependencies; see our guide on installing with npm for more information.