47 minutes ago, Froberg said:

Fair warning for anyone who manages to read this before updating. My transmission update today resulted in the nulling of all download locations, immediately triggering a few TB's of downloads before I caught it. 

Not sure what went wrong, all my settings seem to be there, but the "move to x folder" history was lost and everything was reset to the standard downloads folder. 

 

interesting...Mine seemed to update fine, but i have been using the dev branch for a while, so that could be why

 

Release 4.0

1 hour ago, clowrym said:

 

interesting...Mine seemed to update fine, but i have been using the dev branch for a while, so that could be why

 

Release 4.0

 

I'm sure there can be a myriad of other factors at play.. just figured since I've done nothing to change the container, other than adding a few more folder-mappings, that it might happen to others, too. 

After removing 600+ seeding torrents and restarting the container, it immediately re-added them all again. So I had to remove the .torrent files manually in the appdata directory too. 

Here's hoping it doesn't happen again. It's been rock solid otherwise. 

Mine went fine lol

 

@clowrym sorry to ping you man. But by any chance is the privoxy option not available anymore? That's the only thing that stopped for me, I know not a lot of people use it. My use case is to make sure the searches by jackett happen behind the vpn. 

6 hours ago, gacpac said:

Mine went fine lol

 

@clowrym sorry to ping you man. But by any chance is the privoxy option not available anymore? That's the only thing that stopped for me, I know not a lot of people use it. My use case is to make sure the searches by jackett happen behind the vpn. 

I dont think so, it seems to be working fine with mine.

I am also having problems with privoxy... I had everything set up correctly and working but now it is not. Everything else is working correctly.

On 9/8/2021 at 1:35 PM, gacpac said:

But by any chance is the privoxy option not available anymore? That's the only thing that stopped for me, I know not a lot of people use it. My use case is to make sure the searches by jackett happen behind the vpn. 

So I finally figured it out on my end. When 4.0 came out they apparently switched from tinyproxy to privoxy. While tinyproxy used port 8888 (which my environment variable was set to for it to work), privoxy uses port 8118 in the container. If you did set up an environment variable, make sure that it is using port 8118 in the container and not 8888.

wow oh really!

I think that might been the case, but i'm using PIA with socks5 now to avoid things

HELP!

 

I did something stupid the Mineosnode have two path defined in the docker:

 

I was cleaning up and the folder on my cache drive /mnt/cache/minecraft

Was empty so I made sure the folder was set to the Array and that the folder was present so I deleted the folder on the cache drive

 

Now when I start up Mineosnode I have no server!

BUT when I go to the /mnt/cache/appdata/minecraft/ all the files are there?

 

I tried to change it back but my server is empty when Mineosnode starts up....

 

UPDATE: This fixed it... https://discourse.codeemo.com/t/after-rebooting-my-unraid-server-my-server-disappeared-from-the-ui-but-it-still-shows-as-running/3836/7

Seem this changed my permissions on the files?

Edited October 19, 20214 yr by casperse

After today's update of Transmisson-VPN in transmission I get an error that I can't connect to tracker, whilst the logs end with: Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User, which just keeps on going...

Worked without issues before update, using PIA.

Any ideas?

 

Please ignore, turns out I was on "dev" as opposed to "latest" on which all is good

Edited October 22, 20214 yr by headnail
own fault....

On 10/22/2021 at 9:28 AM, headnail said:

After today's update of Transmisson-VPN in transmission I get an error that I can't connect to tracker, whilst the logs end with: Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User, which just keeps on going...

Worked without issues before update, using PIA.

Any ideas?

 

Please ignore, turns out I was on "dev" as opposed to "latest" on which all is good

Same thing happened to me, and I know I never changed that, so I have no idea how that happened, so thanks for saving me potentially hours of looking in the wrong direction.

On 10/22/2021 at 12:28 PM, headnail said:

After today's update of Transmisson-VPN in transmission I get an error that I can't connect to tracker, whilst the logs end with: Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User, which just keeps on going...

Worked without issues before update, using PIA.

Any ideas?

 

Please ignore, turns out I was on "dev" as opposed to "latest" on which all is good

Jesus. That's really all it was. Was having the same issue and tried troubleshooting every little detail. Saw this and looked at what I was on. Noticed it was on dev and not latest...

I was able to get the MinecraftPE world files off my kid's iPad and I put them where I *thought* they should go in the server after clearing out the default files. No success. Any suggestions would be appreciated.

Anyone having issues launching a 1.18 server??

Things I have tried so far:
-Create new server using official 1.18 profile from MineOS (won't launch or provide log)
-Import server after hosting on win10 pc for testing (Provides log but says failed to load server.properties, failed to load eula.txt and that I need to agree to EULA. Confirmed EULA = true)
-Created 1.17 server and then tried to change files to 1.18 (tried just for fun)

On PC, I had to upgrade to Java 17 for the server to even launch, would this be causing the issue for MineOS?

On 11/30/2021 at 3:19 PM, Willybum said:

Anyone having issues launching a 1.18 server??

<snip>

On PC, I had to upgrade to Java 17 for the server to even launch, would this be causing the issue for MineOS?

Precisely. The version of Java inside the current container is 16. We need an updated container.

Hey guys,

 

Was just about to post the same thing. Since 1.18 was released I can't get the server to start. Spent a while diagnosing the issue and have determined it's as others have mentioned here, the version of Java inside the docker is not up to date. Anyone have an update as to when an update is going to be released for this?

 

Cheers,

 

-Chris

I dont maintain the repository, only the template, please post here Hexparrot's Repository

On 12/4/2021 at 3:00 AM, clowrym said:

I dont maintain the repository, only the template, please post here Hexparrot's Repository

Apologies, will do!

15 hours ago, muntedewok said:

Apologies, will do!

No worries, I have no issue trying to help with configurations, set up etc, but when it comes to the actual container, i cant do much, as its not mine!

 

https://www.zdnet.com/article/security-warning-new-zero-day-in-the-log4j-java-library-is-already-being-exploited/

 

Vulnerability seems to impact all Minecraft Java edition servers.

 

In order to mitigate vulnerabilities, users should switch log4j2.formatMsgNoLookups to true by adding:"‐Dlog4j2.formatMsgNoLookups=True" to the JVM command for starting the application.

 

What is the easiest way to add this in Mineos? I've also posted on Hexaparrot's repository to increase awareness.

On 12/1/2021 at 5:30 PM, coppit said:

Precisely. The version of Java inside the current container is 16. We need an updated container.

Here is he solution I found. 

https://github.com/hexparrot/mineos-node/issues/450#issuecomment-989127314

In the docker console run

apt-get update && apt-get install -y openjdk-17-jre-headless

and then restart the docker container.

The webui of MineOS uses the port "8443" and I've opened that port on my router to my UNRAID server IP, but I am unable to enter the webui from my main PC. I know this is not much to go on for you in terms of helping me, but maybe some one have any tips on what I could try to get it to work?

2 hours ago, amne said:

The webui of MineOS uses the port "8443" and I've opened that port on my router to my UNRAID server IP, but I am unable to enter the webui from my main PC. I know this is not much to go on for you in terms of helping me, but maybe some one have any tips on what I could try to get it to work?

I would need to see your docker run command / settings

7 hours ago, clowrym said:

I would need to see your docker run command / settings

 

Here you go :)

On 1/19/2022 at 12:25 AM, amne said:

 

Here you go :)

Nothing stands out there, How about the container log?

 

Complete Unraid newbie here, moving over from Synology. I'm trying to get Transmission_VPN working on my new Unraid machine and hitting a very basic issue: the container simply fails to start. This is what I see repeatedly in the logs:

Starting container with revision: 85d3b9633607f2d1fd58d21190a84a31a4cea7b8
Creating TUN device /dev/net/tun
mknod: /dev/net/tun: File exists
Starting container with revision: 85d3b9633607f2d1fd58d21190a84a31a4cea7b8
Creating TUN device /dev/net/tun
mknod: /dev/net/tun: File exists

Looking at the Unraid environment I notice that the Transmission_VPN docker is not creating a folder to store the configuration in /mnt/user/appdata/, which is the default set in Docker. I also have installed the Plex docker and that one is working fine.

 

Any ideas? Do I need to manually set the container to create a config?