Jump to content
clowrym

[Support] Clowrym's Docker Repository

136 posts in this topic Last Reply

Recommended Posts

Hi All,

I'm having trouble with the transmission docker:

 

===============================

STARTING TRANSMISSION
CONFIGURING PORT FORWARDING
Transmission startup script complete.
Generating new client id for PIA
Fri Dec 29 19:05:58 2017 Initialization Sequence Completed
Got new port 51897 from PIA
transmission auth required
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Error: portTested: http error 0: No Response

===============================

 

Any idea what I'm doing wrong?

Share this post


Link to post
On 12/29/2017 at 12:07 PM, doubleohwhatever said:

Hi All,

I'm having trouble with the transmission docker:

 

===============================

STARTING TRANSMISSION
CONFIGURING PORT FORWARDING
Transmission startup script complete.
Generating new client id for PIA
Fri Dec 29 19:05:58 2017 Initialization Sequence Completed
Got new port 51897 from PIA
transmission auth required
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Error: portTested: http error 0: No Response

===============================

 

Any idea what I'm doing wrong?

 

Looks like a DNS problem, Can you add dns flag to your template --dns 8.8.8.8

Share this post


Link to post

Any idea why my uptime shows like this? 

 

CapturFiles-Jan-06-2018_09_20_32.png.b8ba4320a77a8d07b49bdb85914bc07e.png

 

Also, how can I enable terminal? I don't see it under Logging @clowrym

Share this post


Link to post
On 1/6/2018 at 10:23 PM, jrdnlc said:

Any idea why my uptime shows like this? 

 

CapturFiles-Jan-06-2018_09_20_32.png.b8ba4320a77a8d07b49bdb85914bc07e.png

 

Also, how can I enable terminal? I don't see it under Logging @clowrym

 

I dont know the issue with the uptime, as I didnt create the app, just the Docker template, To be honest a few commits ago I had the same issue, but I though Hexparrot had fixed it...... I'm not sure what you mean by enable terminal? you can access the docker with  

docker exec -ti MineOS-node /bin/bash

replace MineOS-node with the name of your docker if you've changed it

Share this post


Link to post

@clowrym Thank you for your work and the hint regarding hexparrots change in his update routs. Even though I am very late to the party, I much appreciate it.

 

Does anyone happen to have an idea on why the memory footprint of my single server in the MineOS GUI is blank? Also it seems it does not adopt the -Xmx setting. The available free memory always corresponds to Unraid's memory. It used to be the same as the -Xmx setting. I suspect it changed with an Unraid update a while back.

 

Thanks!

 

 

Share this post


Link to post
On 2/3/2018 at 9:54 AM, Seige said:

@clowrym Thank you for your work and the hint regarding hexparrots change in his update routs. Even though I am very late to the party, I much appreciate it.

 

Does anyone happen to have an idea on why the memory footprint of my single server in the MineOS GUI is blank? Also it seems it does not adopt the -Xmx setting. The available free memory always corresponds to Unraid's memory. It used to be the same as the -Xmx setting. I suspect it changed with an Unraid update a while back.

 

Thanks!

 

 

 

Are you taling about the Server overview? I belvive it will always show unraid's memory value unless you specify the max amount of mem docker is allowed

image.thumb.png.e1a504028cbc03bbb329e63f087f579c.png

 

When you look at an indivdiul server it should be different:

image.thumb.png.10da1bb7eb651179d2959ce1643059fe.png

Share this post


Link to post
44 minutes ago, clowrym said:

 

Are you taling about the Server overview? I belvive it will always show unraid's memory value unless you specify the max amount of mem docker is allowed

 

 

Thanks for your response, I mean the "memory footprint" shown in the server overview. Mine looks like this:

 

mineos.thumb.jpg.4211e99a406b5f214bb0b942f0b6bbe8.jpg

 

The field is empty no matter what I do. Depending on the xmx settings the total available memory shown in the server view seems to change, but knowing the actual footprint would be helpful. As I said, it used to work. I googled around, after all it might be a Mineos issue, but I wasn't able to find something useful. 

 

Share this post


Link to post
1 hour ago, Seige said:

 

 

Thanks for your response, I mean the "memory footprint" shown in the server overview. Mine looks like this:

 

mineos.thumb.jpg.4211e99a406b5f214bb0b942f0b6bbe8.jpg

 

The field is empty no matter what I do. Depending on the xmx settings the total available memory shown in the server view seems to change, but knowing the actual footprint would be helpful. As I said, it used to work. I googled around, after all it might be a Mineos issue, but I wasn't able to find something useful. 

 

 

Can you add a value to Xms and see if it makes a difference?

Share this post


Link to post
43 minutes ago, clowrym said:

 

Can you add a value to Xms and see if it makes a difference?

 

Unfortunately, it makes no difference. :/

Share this post


Link to post

I can't seem to access the interface anymore. Is anyone else having this issue? Maybe related to 6.4.1 that way recently released?

 


STARTING TRANSMISSION
NO PORT UPDATER FOR THIS PROVIDER
Transmission startup script complete.
RTNETLINK answers: File exists
Wed Feb 7 04:29:36 2018 ERROR: Linux route add command failed: external program exited with error status: 2
Wed Feb 7 04:29:36 2018 Initialization Sequence Completed

 

looks like everyone else worked but maybe couldn't add the lan route? Anyone else having this issue?

Share this post


Link to post

I am also having issues after the last few updates, can't say if it was since 6.4.1 but I was pretty sure it was working after that update.  Looks like transmission-daemon isn't starting, and when I start the service manually inside the docker I can get to the web interface but get 404 not found messages, Couldn't find Transmission's web interface files.

 

STARTING TRANSMISSION
CONFIGURING PORT FORWARDING
Transmission startup script complete.
Wed Feb 7 17:41:53 2018 Initialization Sequence Completed
Got new port 36664 from PIA
transmission auth required
[2018-02-07 17:41:53.978] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server
[2018-02-07 17:41:53.992] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server
Checking port...
[2018-02-07 17:42:04.013] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server

Edited by thedman
added logs

Share this post


Link to post
15 hours ago, thedman said:

How exactly do I revert to that version in Unraid?

Change the tag:

 

image.thumb.png.ee6e607a8b55c87aae0430395df25d1d.png

Share this post


Link to post

My VPN is not listed (ExpressVPN) in transmission_VPN, how can I use it ?

 

Thank you in advance

Edited by NY152

Share this post


Link to post

Hi

I've setup a server using your MinecraftPE plugin. It works fine.

 

But I want animals og creatures to spawn in the game. Do you know how I can do that ?

Edited by sosdk

Share this post


Link to post

In the XML for Transmission_VPN, when selected, the word False breaks settings.json.  It must be a lowercase f.  All true and false values in settings.json must be lowercase.

 

<Config Name="RATIO_LIMIT_ENABLED" Target="TRANSMISSION_RATIO_LIMIT_ENABLED" Default="true|False" Mode="" Description="Enable Ratio Limits" Type="Variable" Display="always" Required="false" Mask="false">true</Config>

Share this post


Link to post

Running your Transmission VPN docker...whenever it's up and running it seems somehow it's eating traffic directed at other dockers.  Running nginx on container 80, host 8081, and traffic forwarded from 80 --> 8081 on my router...no traffic ever reaches my nginx docker while transmission is up.

 

Oddly, it's only external traffic.  Traffic from within my network directed at 8081 gets to the appropriate docker fine.

Edited by NeoMatrixJR

Share this post


Link to post
On 3/15/2018 at 4:30 AM, JoeManiac said:

In the XML for Transmission_VPN, when selected, the word False breaks settings.json.  It must be a lowercase f.  All true and false values in settings.json must be lowercase.

 

<Config Name="RATIO_LIMIT_ENABLED" Target="TRANSMISSION_RATIO_LIMIT_ENABLED" Default="true|False" Mode="" Description="Enable Ratio Limits" Type="Variable" Display="always" Required="false" Mask="false">true</Config>

 

Fixed, Thanks for the heads-up

  • Upvote 1

Share this post


Link to post
On 3/16/2018 at 3:55 PM, NeoMatrixJR said:

Running your Transmission VPN docker...whenever it's up and running it seems somehow it's eating traffic directed at other dockers.  Running nginx on container 80, host 8081, and traffic forwarded from 80 --> 8081 on my router...no traffic ever reaches my nginx docker while transmission is up.

 

Oddly, it's only external traffic.  Traffic from within my network directed at 8081 gets to the appropriate docker fine.

 

I'm not sure what could be causing this one..... I'll have to do a little research.

Edited by clowrym

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now