Hey all, I did check for an immich sub first, but you smart people seem to be my only option now reddit has banned me for refusing to give them an email address.

Background: So, I have a Ugreen DH2300 NAS it runs a cut down version of debian. I've got docker running on it, which is happily hosting Jellyfin. Basic config of the drive volume is from root I have a docker tree and also a data tree. Immich & Jellyfin under docker, movies pictures tvshows books under data. I have pictures indexed by Jellyfin and it works but it isn't great. I have a vanilla copy of immich up and running, I can upload via web browser a pic at a time. The vanilla config puts those files in ./volume1/docker/immich/library/upload/very-long-random-number-directory

Where volume1 is the mounted displayed nas volume (from the nas host it's /mnt/volume1 if you ssh in)

Problem:

I have a terabyte of pictures under ./volume1/data/Pictures that is not visible in docker

Importing 1 by 1 via web browser is obviously not ideal. It also copies the set of pictures from one directory on the NAS volume to a duplicate under library/upload - not great for space.

I've seen the CLI tool exists and if I ssh into the NAS I can see the /Pictures directory as well as the docker/immich/library etc directory but it also has the downside of duplicating all the photos into the immich directory

Ideally I'd like to just index it like jellyfin does when you add files to movies or tv shows. I can't seem to even find a way to point the docker instance to the folder (i modified the .env file but it ignored it, so obviously got that wrong).

Is this the only way ?

EDIT Thank you all for the quick responses - I somehow managed to break the container altogether, so I'll reinstall from scratch and then add your suggested "external folders" config and see how I go.

Thanks again

OK, now here's a curly one for you all.

I posted earlier about added the timezone parameter to my jellyfin docker container:

https://literature.cafe/post/31010564

Thanks again for your help, but I still have an issue...

So the Debian host (ugreen DH2300 NAS) shows the correct time (UTC+1), and now, thanks to the TZ= parameter added above if I go to the terminal for the container (docker app, select container, select jellyfin, select settings, go to terminal tab, launch bash) then a date command also shows the correct time / same as the host and my PC

Here's the weird part though - the jellyfin dashboard (the gui) STILL shows the UTC time, not the UTC+1 daylight saving time. I.E 1 hour earlier than actual/correct time.

For the avoidance of confusion, I had to restart the container to get the timezone parameter loaded. So it has definitely been restarted with it.

Any ideas where the setting is to get it to report correctly ? I mean it's not a big deal but it's niggling at me.

I've run up a copy of Jellyfin in docker on a cheap NAS about a month ago. Seem to have mostly sorted out the wrinkles. First time running docker or jellyfin (all my other selfhosting has been on bare metal not using docker).

ONE issue: Timezone (daylight saving).

The NAS host OS is correctly showing the local TZ with 1 hour shift post daylight saving at the end of March - I checked at a command prompt (it's a tweaked version of debian) that it's showing correctly.

The Docker container however is showing the base time before daylight saving (ie UTC vs UTC+1)

I've just worked through how to change the docker compose file to pick up the correct TZ ie putting a

TZ: "Europe/London"

In the compose file (Project, settings, compose configuration)

BUT

When I go to apply it (redeploy button), it gives me a warning that makes me nervous to push it out.

"Redeployment will delete unneeded containers and images"

Soooo...will hitting deploy wipe out all the configuration I've done and the days worth of indexing all the media the server has done ? Or am I being overly nervous ?

Hey all, I hope I'm on topic, I host a bunch of self hosted services at home, however with the way things are going in the UK I'm looking to get a VPS set up, initially to use as a proxy and wireguard pop, probably move more stuff to avoid censorship later on (use case is a little fuzzy just yet).

So, primary question is - any suggestions for good VPS providers that aren't the big 3 tech bros, in Western Europe, preferably France, Netherlands Belgium or Spain ?

Secondary question, my ISP throttled all VPN traffic the other week, we have 3 different VPN providers (2 mainstream 1 small player) across about a dozen devices they were all throttled to 250K. If you turned VPN off or split tunneled it went back to 100mb plus (I have a 1Gb connection).

When I asked on reddit for advice the reddit bots immediately jumped in with "oh it's just your VPN provider" however if I dropped phones off the wifi and connected to mobile telephony the VPN'd connections were fine - similar speed to split tunnel less some overhead. Lasted for 12 hours and then went back to normal. I assume I was being sin-binned for too much sailing of the seven seas.

Any idea what settings I can tweak to make it harder for them to throttle me ? I tried changing the Mullvad one to use port 443 but it didn't affect the throttling - maybe they'd already put the throttle on for anything encrypted by that point ?

Edit to fix poor grammar

Edit 2 - thank you all so much for the rapid replies, I'm going with OVHCloud as the cheapest option at my desired spec, with Ionos as the fallback if I have any issues with it.

The list you guys gave was brilliant though, so many options. Really appreciated

Aukus had a less than immaculate conception. It was conceived in secrecy and born in haste, a tribute to political opportunism and a travesty of disciplined planning. The enthusiasm of theatrical announcements notwithstanding, it was in trouble from the beginning. The US Navy had serious doubts about both the ability of US shipbuilders to deliver submarines in any workable timeframe and the ability of the Royal Australian Navy to integrate and operate them. That was not a question of trust but of capacity – on both sides.

And, of course, experienced and well-informed Australian defence planners rang the warning bells from the beginning.