Thanks for the rec. I’ve got all my stuff running through NPM and am loath to change it just for this one (annoying) thing!

Ah, thank-you so much!

Yeah see I’m not even sure what the env vars are. I’m running it with docker-compose and the only alterations I’ve made to anything are to add my IP address to the config file in the trusted domains array. That’s definitely where it needs to go because if I take it out then it flops hard.

Actually this fixed it. Thanks! They can access if I share it but NOT if I add them as a user and then share it. I had to delete them as a user first 🤷‍♂️

Even that doesn’t work. I’ve made them an admin on the machine but they get a message saying they already have access to it. But … they don’t!

Yep. It says they are a member of my network. But no dice.

Replying to my own comment to say thanks again for all the tips and advice. I got it all sorted with Tailscale. The final piece of the puzzle!

Ah, I very much did not know that! Ok, I’m off to investigate Tailscale a bit more.

Thanks a lot. Tailscale is out, unfortunately. Because the server also runs Plex and I need to use it with Chromecast on remote access (it’s an old CC, so can’t add tailscale to it). Looking into Cloudflare and port forwarding. I’ve just signed up to NextDNS though, so don’t want to add another layer of DNS stuff to my mix.

Thanks, I’m going to try this.

Thanks, I’m going to try the port forwarding part. That seems like the simplest step. NPM looks very useful though.

This looks really useful. Thanks!