binhex

wow a 2015 thread, old school :-), maybe this needs locking moderators?

with the vpn off the container will not use the specified name servers defined in NAME_SERVERS value, it will instead use the name servers defined on the unraid host, which are obviously permitted by your firewall, you could try setting NAME_SERVERS to the same value as the name servers defined on your unraid host, this should allow it to work.

the key bit of info missing :-), ok if you want to be able to access the web ui whilst out and about then you need to add your VPN network range to the LAN_NETWORK value, for instance assuming your VPN allocates a network of 192.168.2.0/24 and your LAN network is 192.168.1.0/24 your LAN_NETWORK value would be:- 192.168.1.0/24,192.168.2.0/24

ok try accessing web ui from another machine/device, try different browser too, also just to double check the network type for the container should be set to 'bridge' is this the case?.

its fairly simple, let me see if i can break it down for you:- start container and log in to server as the minecraft user you want to be the operator check log file /config/minecraft/logs/screen.log and make a note of the xuid value for the minecraft user create/edit file (use notepad++ NOT notepad) /config/minecraft/permissions.json and put the following contents in the file, replacing xuid with the value you found in step 2:- save the file and restart the container. [ { "permission" : "operator", "xuid" : "<my xuid number from step 2>" } ]

well you can def see the dns resolution failure in your screenshot above, to confirm left click deluge icon and select 'console' then type 'ping www.google.com' and that should failto resolve, now the question is what on your lan is blocking it.

that log shows a successful start, is the ip of the machine running the web browser in the 192.168.1.x range?.

did you try this?

please dont generalise, what might look like everybody has the same problem (cant access web ui) there are literally dozens of reasons for this, please do the following to help identify the problem:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Something is preventing DNS lookup on your LAN, recheck pfsense, pi hole etc, also you might want to remove the PIA name servers, they are very unreliable recently, so change NAME_SERVERS to have a value of:- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1 Sent from my CLT-L09 using Tapatalk

I pulled down the latest image and checked the version in the web UI and it was up to date so you must have been targeting a specific tagged version would be my guess. Sent from my CLT-L09 using Tapatalk

my only thoughts are, where is the tuner card running?, is one running the tuner card via windows and the other time running via unraid? if so it could be a driver related problem.

10.7.7-1-01 is latest tagged release, are you up to date?.

or simpler still, left click edit sonarr icon, change something, change it back to what it was, scroll to the bottom and click apply, this will delete the now duff container and re-create it and you should be back to a good state.

Never seen this, nope Sent from my CLT-L09 using Tapatalk

assuming both containers have separate HOST ports defined i would suspect your system cannot cope with running two minecraft servers at the same time probably due to underpowered CPU, thus the overloaded message shown in the first screenshot.

this is a bug in code-server, its hopefully going to be fixed, for the time being roll back to tag version '3.12.0-0-01' if you dont know how to ref a tag then see Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

crank up the logging and watch for anything that blocks.

from your log this is the issue:- [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' running pihole/pfsense/opnsense? if so check you arent blocking that url, thats the most common cause, it is also entirely possible PIA was having a bad day, so just try it again.

I appreciate the detailed explanation of the memory usage increase that is very interesting, I haven't run 4.4.x yet so I haven't seen any memory increase, expected or otherwise, so it's nice to hear it isn't a bug. Sent from my SM-T970 using Tapatalk

no idea on that front, but the memory leak persists in 4.4.1, word to the wise, stick on 4.3.9 for the time being:- https://www.reddit.com/r/qBittorrent/comments/suuoi3/does_441_fix_440s_memory_leak_issues/

i have port forwarding setup for this image myself and can get people to connect external to my home lan, here is a screenshot directly from my router (pfsense), nothing too exciting here, pretty much a standard port forward:- NAT rule:- firewall rule:-

thanks for letting me know, not sure what i can do about that 🙂

you could try installing knock on unraid:- https://packages.slackonly.com/pub/packages/current-x86_64/network/knock/

change that to /downloads