Hi,

The clone has a different IP address

Hi, thanks for your reply.

when I run mount -a -vvv I get the following:

mount.nfs: timeout set for Tue Aug 8 16:14:10 2023

mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.188,clientaddr=192.168.0.116' mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.188,clientaddr=192.168.0.116'

mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'vers=4,addr=192.168.0.188,clientaddr=192.168.0.116'

mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'addr=192.168.0.188'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.0.188 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 192.168.0.188 prog 100005 vers 3 prot UDP port 661

mount.nfs: mount(2): Permission denied

mount.nfs: access denied by server while mounting 192.168.0.188:/mnt/store/test-share

Hi, thanks for your reply.

Lets call the original Proxmox container CT1 and this has the *arrs Dockers that can access and interact with the NFS share on TrueNAS

Lets call the new Proxmox container CT2 and this is the one giving me the can’t access error

Lets call the cloned Proxmox container CT1Clone, this one can access the NFS share.

I think the NFS share is not restricted to any IP address, this is a screenshot of the NFS permissions. https://i.imgur.com/9k5jnw4.png I can also access if from my Windows machine that also has a different IP address.

CT1 & CT1Clone work fine, CT2 doesn’t work.

My Raspberry Pi’s are named after planets and large bodies on the Solar system.

My servers are named after The Expanse characters and ships.

VM’s and CT’s after their usage with a tag in Proxmox for the OS used.

It depends on how busy the roundabout is.

If it’s really busy and there is a possibility of traffic backing up on either of the the two exits before the one you want to take then I’d be in the righthand lane on approach and move to the lefthand lane as soon as I’m past the second exit, getting in the lane marked A610 going under the bridge. This way you avoid possibly getting caught in slow moving traffic and adding to the back up.

If the roundabout isn’t that busy then using the lefthand lane on approach would be fine and just staying in the lefthand lane all the way.

Roundabouts need to be as free flowing as possible, so use whichever lane is going to keep the traffic moving best.

I use a roundabout everyday that crosses a motorway and the traffic joining the motorway always backs up the slip road on to the roundabout at rush hour. Often people wanting to go “straight” over the roundabout get in the lefthand lane on approach and then get stuck in the backed up traffic which just adds to the congestion. I tend to approach in the righthand lane and move to the left once past the motorway exit. I’ve noticed that people tend to leave a gap for the traffic in the righthand lane to go through but will block the lefthand lane just in case someone sneaks in front of them!! LOL

Thank you again. Yeah, I’m trying this from home as opposed to a vps. It’s more as a learning exercise than a serious instance.

I’m still going to try and getting it working behind my reverse proxy, like I say, as a learning experience.

Thank you so much for replying.

I think this is above my skill level, but I will have a read through your advanced configuration page and see if I can understand it.

Thanks again, but I think I’m going to need more than luck!! LOL

Hi @ubergeek77@lemmy.ubergeek77.chat

I must be doing something wrong here because unlike many others I can’t seem to get this working! Please can you offer some advice?

I have amended the config.env file to change the HOSTNAME, SITE NAME and ADMIN USER but left everything else the same.

I then ran ./deploy.sh and everything seems to have worked because it presented me with the admin login credentials and basic instructions to shutdown and start the instance. I tried simply typing the IP address of the docker container in to a browser but that didn’t work and TBH I didn’t expect it to. I then typed the URL into the browser and I’m getting a “ERR_TOO_MANY_REDIRECTS” error message. I read through the trouble shooting on your Github but the only reference to too many redirects mentions a Cloudflare API token, I’m not using Cloudflare nut I am using nginx proxy manager to point my URL to the docker container.

I hope some of this makes sense.

Saddest uninstall ever!! 😪