binhex

this is highly unlikely to just stop working, there have been no code changes whatsoever in this area for a very long time!. what is the value of LAN_NETWORK now?.

its not an issue with the docker image, this is an unraid split level issue, its PROBABLY to do with high-water and the inclusion of specific drives, one is probably trumping the other and causing the writes to other drives, you are best off asking this in the general support thread as im no expert on this.

You can't rush art [emoji16] Sent from my CLT-L09 using Tapatalk

yep running any minecraft server v1.7.1 to v1.18.0 will expose you to the vulnerability, so that def explains why it happened. So i've done what i can here, i have spammed all Minecraft Java support threads that i own with a warning and what to do to patch, i have also automated patching of binhex/minecraftserver, however its not possible for me to automatically patch mineos-node or crafty (multi minecraft server frontend), as configuration for each server is done through the server web ui and thus must be done by the user for each running minecraft instance.

IMPORTANT - Log4j Vulnerability There has been a report of a user running an unpatched version of Minecraft Java which was also exposed to the internet, this resulted in the log4j vulnerability being exploited and the user suffering from a hack against files exposed for the container (located in /config). All users PLEASE keep in mind, if you wish to expose Minecraft servers to the internet then you must either:- 1. Ensure you are running Minecraft jar based off Minecraft v1.18.1 or later (recommended). or 2. You must mitigate the vulnerability by following this document:- https://help.minecraft.net/hc/en-us/articles/4416199399693-Security-Vulnerability-in-Minecraft-Java-Edition Note:- binhex/minecraftserver users - I have done my best to automatically patch Minecraft according to the document linked above by detecting the version of minecraft jar and then patching accordingly, However it is up to the user to ensure the patching is correct and there are no new vulnerabilities found.

IMPORTANT - Log4j Vulnerability There has been a report of a user running an unpatched version of Minecraft Java which was also exposed to the internet, this resulted in the log4j vulnerability being exploited and the user suffering from a hack against files exposed for the container (located in /config). All users PLEASE keep in mind, if you wish to expose Minecraft servers to the internet then you must either:- 1. Ensure you are running Minecraft jar based off Minecraft v1.18.1 or later (recommended). or 2. You must mitigate the vulnerability by following this document:- https://help.minecraft.net/hc/en-us/articles/4416199399693-Security-Vulnerability-in-Minecraft-Java-Edition Note:- binhex/minecraftserver users - I have done my best to automatically patch Minecraft according to the document linked above by detecting the version of minecraft jar and then patching accordingly, However it is up to the user to ensure the patching is correct and there are no new vulnerabilities found.

IMPORTANT - Log4j Vulnerability There has been a report of a user running an unpatched version of Minecraft Java which was also exposed to the internet, this resulted in the log4j vulnerability being exploited and the user suffering from a hack against files exposed for the container (located in /config). All users PLEASE keep in mind, if you wish to expose Minecraft servers to the internet then you must either:- 1. Ensure you are running Minecraft jar based off Minecraft v1.18.1 or later (recommended). or 2. You must mitigate the vulnerability by following this document:- https://help.minecraft.net/hc/en-us/articles/4416199399693-Security-Vulnerability-in-Minecraft-Java-Edition Note:- binhex/minecraftserver users - I have done my best to automatically patch Minecraft according to the document linked above by detecting the version of minecraft jar and then patching accordingly, However it is up to the user to ensure the patching is correct and there are no new vulnerabilities found.

I tell ya what, I will firstly put a big fat warning on my threads and secondly I will see if I can detect the version of Minecraft jar, if so I can attempt to patch for the user using the guidance in the link above. Edit just to be clear, anything running Minecraft Java is potentially vulnerable when using earlier versions, so mineos-node and crafty images are also prone when not running Minecraft server latest versions. Sent from my CLT-L09 using Tapatalk

Correct, latest version is built automatically and is the default version included with the image. Sent from my CLT-L09 using Tapatalk

as im sure anybody who runs minecraft java is aware (well reported on the internet), minecraft was highlighted as having the log4j vulnerability, this was then patched by mojang and quickly released, but obviously the patch and fix is only available for the current latest version of minecraft java, if you run earlier versions then you are still vulnerable, im assuming the OP was indeed running a version prior to the fixed version (1.18.1), there are according to mojang certain mitigations you can do for earlier versions, but this would be up to the user to perform these, link to doc:- https://help.minecraft.net/hc/en-us/articles/4416199399693-Security-Vulnerability-in-Minecraft-Java-Edition so as far as damage limitation goes, as long as the OP did not add any additional volume binds then it will be limited to /config only, so a quick restore from backup or at worst, copy your world somewhere, then delete everything in /config, fix up to prevent the vulnerability and restart container and copy the world back should suffice.

sadly unless you configured the backup path correctly then your backups are lost, the default location saves to a path inside of the container (default defined by crafty dev not me), you need to reconfigure this to save to a volume bind that saves to the host, for example /config/crafty/backups however as your world will of been stored on /config if you have plugin 'Appdata Backup/Restore v2' or manually backup your docker config (you really should be doing this) then you should be able to restore your config for crafty and thus restore your world. edit - to prevent the potential of this happening again im going to symlink the default path to /config which is really the only option, as the backup path is saved to sqlite db and thus unable to edit easily.

lol, err it really isnt 🙂

@dyno @Cpt. Chaz the solution is simple, add the vpn network range to LAN_NETWORK, for example assuming a vpn network of 192.168.10.x and a lan network of 192.168.1.x i would define LAN_NETWORK as follows:- 192.168.1.0/24,192.168.10.0/24 if you need more networks, just keep adding them comma separated. edit - gonna turn this into a faq.

ok cool.

yeah dont worry about the 'Name' of the variable its of no significance, its the actual 'Key' and 'Value' for the variable that matters.

sorry just to double check, you CAN get to the web ui via the custom port by entering it directly into your web browser, its just the 'web ui' link when you left click the icon that isnt working, right?

yep yours looks correctly set, try a different browser, if that works then its probably a caching issue, if it doesnt work try a restart of unraid, if STILL no go then you need to raise this in the general support section of the forum, as the web ui link is an unraid function not related to this image.

done, sadly this wont stop the upgrade from appearing on first startup for brand new users (config file doesnt exist therefore cannot be edited), but it will stop any future upgrades for existing users with existing config.xml files - best i can do.

i think there is some confusion here, so you need to set 'variable' (not 'port') with key name WEBUI_PORT and the 'value' has to be the port number you want, this variable should already exist, you want to set the value to 8081. next up you need to 'remove' the 'port' for 8080 for this container, then add a 'port' and set it to 8081 for 'container port' and 'host port', dont worry about setting anything else. last step is to edit the 'WebUI' entry (requires 'advanced view' toggled on) and set the port to 8081 (see my previous screenshot above). if you are still stuck then switch on 'advanced view' and post a screenshot showing all settings, mask out username and password though.

cool, thanks for the donation, its appreciated.

no idea on the mismatch, even when assuming bits vs bytes thats a big difference, the encryption overhead im seeing is around 5-10% max, so its pretty low and not what you are seeing. just some other things you can try, take a look at Q6 regards tweaks to improve dl/ul speeds:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

nope that is not necessary, so def dont do that, does qbittorrent give you a hint as to the issue?, i see they are in an 'errored' state, expand/click on it and see if it gives you a hint as to the issue. btw port forwarding all looks good to me, you could also rule out permissions issues here by temporarily setting the incomplete location to /tmp, this will then write downloads to fs inside the container, if it improved things then you know the issue is related to the volume bind for /data (permissions or filesystem issues).

ok so port forwarding is not your issue here, as you are using pia and its scripted to do it all for you, ensure that the 'VPN incoming port is XXXX' matches the port shown in the web ui for qbittorrent, if that looks ok (which i expect it will) then just verify that your incomplete and completed folders are also set correctly, screenshot would confirm this.

sounds very much like a port forwarding issue, lets being with some logs, do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

the above all looks good to me, however i dont see a screenshot confirming you have change WEBUI_PORT env var, this is important and must also be changed, in your case to 8081, screenshot showing mine (2100 for me):-