JASN_DE

There is no need to run Traefik if you already have a working reverse proxy. Also, unless your nginx is running on non-standard ports, the ports 80 and 443 should not be available for traefik, which will prevent it from working correctly.

You can narrow it down: attach to the container, this’ll give you a life “feed” of all messages the container produces. Then with that running, open your app and see if the container has anything to say about the sync process.

As always: have you checked the logs?

Not for a Synology, but I doubt Hetzner cares where the data comes from. Works well, especially once you got the keys in place. Have stored and restored, it’s a simple file storage.

As much as I hate it, I think I’ll have to go through the logs after all.

Selfhosting without checking the logs to hunt down errors? That’s not going to be pretty.

Let’s Encrypt is fully automated and will issue certificates as long as you provide an email address AND have a proper, working config. Don’t get stuck on that email “issue”, your problems will lie somewhere else.

As always when problems arise: check the log files.

No, the other details. Devices, browsers, operating systems, etc.

Depends. More details please.

I haven’t tested that part of it yet, but the self-hostable StirlingPDF offers conversion from PDF to a number of formats.

The rest I use it for works fine, so maybe that could be an option.

If you’re doing a fresh instance it will solve a lot of issues. Personally I run a Nextcloud instance which got its own 2TB SSD. I mounted the disk at /nextcloud, then used bind mounts in docker compose for db and NC.

Which part is your problem, serving the media from disk, or transcoding and serving that stream?

A big portion of that is caused by the drives, so you’d have to compare the empty QNAP vs your empty machine. Also, depending on which NAS appliance, check that the CPU is actually powerful enough to run all your services.

will all my Jellyfin traffic go through the VPS and count as bandwidth used?

Yes.

“Cloud” simply means it’s on other people’s machines.

No. Why do you think it is?

Back when I started this compatibility with clients was an issue; but I don’t use Android anymore. In any case, is this still an issue?

Um… How are we supposed to tell you if your unnamed DAV client will have problems with your unnamed new DAV server? Works fine for me.

Incredibly rarely, and not as a part of everyday life. The few notes I take are usually digital as part of my work.

And basically useless if you need external users to be able to connect to the services.

In addition to the explanation you got from the other user: once you’ve set up the bouncer middleware in the configs (don’t know if there even exists a good way to do that outside of the configs files), you simply assign the middleware in the compose file as usual.

What languages do you speak?