• 4 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle


  • 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.







  • 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.