binhex

and i assume you have a NextCloud docker container right?, if so it will be that container that is generating files/folders with user/group sshd not syncthing.

https://forums.unraid.net/topic/71764-support-binhex-krusader/?do=findComment&comment=1282910

Which folders are we talking about here? Give the full path Sent from my 22021211RG using Tapatalk

Obviously I didn't include a crypto miner in the image, no sign of xmrig for me, sounds like a possible security breach on your server. Sent from my 22021211RG using Tapatalk

if you get dns failure then the vpn tunnel is down (dns blocked on lan), once the tunnel is down natpmp will also fail as it requires a working vpn tunnel to get assigned an incoming port. so the question is, why is the tunnel going down, well there are a number of possibilities, as you mentioned it could be protonvpn getting overloaded, try and choose an endpoint with low utilisation (noticed protonvpn show this in their endpoint selection webpage). one other thing to mention is that i have code in place to recover from a vpn connectivity failure, so you should see an attempt to re-establish the vpn tunnel and subsequent natpmp calls to get a new incoming port, have you tried simply leaving the container running to see if it recovers?.

nordvpn user with auth failed, this is well known, nordvpn changed their authentication mechanism you need to get the new credentials. edit - follow this guys post:- https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1278020

It was as I suspected fiddly and to prevent me coding blind I signed up for 1 month of proton VPN, I'm quite pleased with the result, it certainly worked well for me. Sent from my 22021211RG using Tapatalk

this is your key bit of info, its telling you you already have that port in use on the host side, if you dont see another container running with that port number then a quick reboot of your server will fix it.

That screenshot shows nothing is wrong. Sent from my 22021211RG using Tapatalk

Just to say, that is a workaround, openvpn is telling you your VPN provider is using weak security, by setting that option you are in effect saying you don't care. Sent from my 22021211RG using Tapatalk

ProtonVPN support is now in!, the image (just built - please pull down) will now automatically assign and set an incoming port for you in the application, support for both wireguard and openvpn is included, for instructions see Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

that is not correct, no, if you set PUID to 99 and PGID to 100 then it will in effect be reading/writing to the array as user 'nobody' and the group 'users'. Go to 'terminal' of your unraid server (not container) and type the following and paste the result: ls -al '/mnt/user/Movies/Extraction 2 (2023)' that doesn't surprise me, the default user you will attach to the running container as is root, and if your permissions are set wrongly on your media to root then that would explain it.

ok so you have had a working incoming port assignment at some point then, yes?

so, you got a valid incoming port assigned to you from protonvpn via the method described in the 'manual configuration' from this site?:- https://protonvpn.com/support/port-forwarding-manual-setup/ perhaps the port was closed due to not refreshing every 60 seconds? taken from the link above - 'Port forwarding is now activated. Note that closing your terminal window will terminate the loop process. You will need to re-run this loop script each time you want to start a new port forwarding session, or the port will only stay open for 60 seconds. '

yeah for obvious reasons a mullvad wireguard config file will not be compatible with PIA, so removal is the correct course of action.

that should be all you need to do, do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Are you connecting to a protonvpn endpoint that supports port forwarding?

did a bit of googling and stumbled across this closed issue, can you try all suggestions mentioned here:- https://github.com/sct/overseerr/issues/2788

well f*ck me!, that's a detailed explanation if ever I saw it!, I am simply packaging up what is available to me, so I'm unclear as to how this is specific to the image I produce, hmmm. if you are running my plex image in the default mode (host mode) then all ports will be open, if you aren't using my plex image then please detail which one you are using.

Ah I'm that case you are in the wrong support thread, this is for Minecraft Java server not bedrock Sent from my 22021211RG using Tapatalk

That warning message normally indicates something is busy reading and/or writing to your plex database which then is causing your system hang, take a look at the processes running on your system and look at the plex log to try and identify what is causing the database to be busy.

I've not seen this issue myself with latest tagged image, make sure you have no 3rd party addons installed, if it's still causing an issue then your best bet is to post the issue on the official plex forum:- https://forums.plex.tv/

I'm also doing nVidia GPU transcoding using a P2000 with the latest image, no issues here AFAIK, your best bet is to post on the plex support forum here and see if they can debug your issue further.

then you are either not using my image or you are trying to run pacman from the hosts terminal and not from the console of the container.

looking at the error i would say that mod is for bedrock server not java minecraft server, so you will probably need to run a bedrock server if you want to do that (see ca).