schmurnan

I'm sure I'm massively overthinking this, but any help would be greatly appreciated.

I have a domain name that I bought through NameCheap and I've pointed it to Cloudflare (i.e. updated the name servers). I have a Synology NAS on which I run Docker and a few containers. Up until now I've done this using IP addresses and ports to access everything (I have a Homepage container running and just link to everything from there).

But I want to setup SSL and start running Vaultwarden, hence purchasing a domain name to make it all easier.

I tried creating an A record in Cloudflare to point to the internal IP of my NAS (and obviously, this couldn't be orange-clouded through CF because it's internal to my LAN). I'm very reluctant to point the A record to the external IP of my NAS (which, for added headache is dynamic, so I'd need to get some kind of DDNS) because I don't want to expose everything on my NAS to the Internet. In actual fact, I'm not precious about accessing any of this stuff over the internet - if I need remote access I have a Tailscale container running that I can connect to (more on that later in the post). The domain name was purely for ease of setting up SSL and Vaultwarden.

So I guess my questions are:

• What is the best way to go about this - do I create a DDNS on the NAS and point that external IP address to my domain in Cloudflare, then use Traefik to just expose the containers I want to have access to using subdomains?
• If so, then how do I know that all other ports aren't accessible (I assume because I'm only going to expose ports 80 and 443 in Traefik?)
• What do other people see (i.e. outside my network) if they go to my domain? How do I ensure they can't access my NAS and see some kind of page?
• Is there a benefit to using Cloudflare?
• How would Pi-hole and local DNS fit into this? I guess I could point my router at Pi-hole for DNS and create my A records on Pi-hole for all my subdomains - but what do I need to setup initially in Cloudflare?
• I also have a RPi that has a (very basic) website on it - how do I setup an A record to have Cloudflare point a sub-domain to the Pi's IP address?
• Going back to the Tailscale thing - is it possible to point the domain to the IP address of the Tailscale container, so that the domain is only accessible when I switch on the Tailscale VPN? Is this a good idea/bad idea? Is there a better way to do it?

I'm sure these are all noob-type questions, but for the past 6-7 years I've purely used this internally using IP:port combinations, so never had to worry about domain names and external exposure, etc.

Many thanks in advance!

I’ve got my library just as I want it, and have made a couple of changes to the in my movies’ .nfo files.

This is fine for a day or so, and then Jellyfin decides to overwrite my .nfo files.

I have them set to “lock” via tinyMediaManager but it doesn’t seem to make any difference. Every day it’ll reorder some movies in my library.

Pretty sure I’ve also disabled the image plug-ins in the library so it shouldn’t be pulling any metadata from anywhere.

Not a huge deal but incredibly frustrating — I want my library showing movies in a certain order and it’s driving me nuts when they’re rearranged 🤣

Any ideas?

TIA.

Just wondered what people are using for their password management.

I’m currently using 1Password on a family subscription for both password management and 2FA (and then Authy for the 1Password 2FA). But I’m seeing a lot more posters — particularly since joining Lemmy — championing BitWarden (either cloud or self hosted) and Raivo OTP as a cheaper, almost-as-functional alternative.

So is it worth the switch? Will I lose out on anything by doing so?

I’m currently running BitWarden with a free account to see if I can live with it. But I must admit, 1Password is a staple app for me and one that I would say is priceless to my workflow and setup.

Just interested in your thoughts and trying to stimulate conversation!

As a recent convert from Plex to Jellyfin, I’m going through my library correcting metadata, etc. and wondered what great ideas I could glean from the community.

I don’t use collections (should I?) because, at least on Plex, I could never completely agree with myself on what should be included in a collection and what shouldn’t.

At present I tend to just sort movies alphabetically (and then in order of release, i.e. 47 Meters Down comes before 47 Meters Down: Uncaged) and I use the sort title for that. But what do you guys suggest with things such as the Star Wars movies, or Indiana Jones movies — movies that don’t have similar titles, e.g. “Star Wars”, “The Empire Strikes Back”, “Return of the Jedi” — would you have them scattered alphabetically around your library, or would you use the sort title to call them “Star Wars 1”, “Star Wars 2”, etc. so they’re all grouped together (albeit breaking the alphabetisation)?

Any other hints and tips would be appreciated!

Hey all,

I'm sure I'm massively overlooking something, but wondered if someone could help me out, please?

I'm trying to switch from Traefik to Nginx Proxy Manager on my Synology NAS, and I've opted to run NPM via a bridge network and a macvlan, so as to not have to mess around with ports 80 and 443 on the NAS (usually reserved for Synology services).

I've got the following:

Bridge network (npm_bridge):

• Subnet = 192.168.10.0/24
• IP range = 192.168.10.2/32
• Gateway of 192.168.10.1.

Macvlan network (npm_network):

• Subnet = 192.168.1.0/24 (same as my LAN)
• IP range = 192.168.1.216/32
• Gateway = 192.168.1.1 (same as my LAN).

NPM is connected to these two networks, and I have a MariaDB container connected to the host - everything works great with NPM and MariaDB - no issues.

However, I have a third network, medianet:

• Subnet = 192.168.96.0/24
• Gateway = 192.168.96.1.

Connected to that network I have a Gluetun container (via docker-compose).

I then have multiple other containers that run through the Gluetun container (several "arrs" and Portainer) using network_mode: service:gluetun.

What I used to have via Traefik was a local hostname I created (let's say, nas.local for posting's sake) and I could simply create labels in my docker-compose for each service to assign ports. I could then access all of these containers via nas.local/portainer, nas.local/sonarr, etc. and they would be accessible via the VPN container.

However, I'm completely stuck on how to do this via NPM. I've tried all kinds of combinations via the Proxy Host configuration, but I don't know how to set it up.

• Do I need an overarching nas.local entry as the top level? If so, what hostname/IP and port combination do I use?
• Do I think setup Custom Locations behind it, one for each service, i.e. Portainer? If so, what is the hostname/IP and port for this?
• Or do I create a new Proxy Host per entry, i.e. portainer.nas.local?
• Do I even need to have Portainer behind the VPN as well, or do I add that direct to the medianet network, and then somehow link NPM to the medianet network as well?

I'm really at a loss, and as it stands all my containers are offline at the moment because I can't figure out how to connect them (except Homebridge and MariaDB - they're both up as they're connected to the host network).

Any help would be very, very much appreciated.