December 29, 20178 yr Hi All, I'm having trouble with the transmission docker: =============================== STARTING TRANSMISSIONCONFIGURING PORT FORWARDINGTransmission startup script complete.Generating new client id for PIAFri Dec 29 19:05:58 2017 Initialization Sequence CompletedGot new port 51897 from PIAtransmission auth requiredlocalhost:9091/transmission/rpc/ responded: "success"Checking port...Error: portTested: http error 0: No Response =============================== Any idea what I'm doing wrong?
January 2, 20188 yr Author On 12/29/2017 at 12:07 PM, doubleohwhatever said: Hi All, I'm having trouble with the transmission docker: =============================== STARTING TRANSMISSIONCONFIGURING PORT FORWARDINGTransmission startup script complete.Generating new client id for PIAFri Dec 29 19:05:58 2017 Initialization Sequence CompletedGot new port 51897 from PIAtransmission auth requiredlocalhost: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
January 7, 20188 yr Any idea why my uptime shows like this? Also, how can I enable terminal? I don't see it under Logging @clowrym
January 8, 20188 yr Author On 1/6/2018 at 10:23 PM, jrdnlc said: Any idea why my uptime shows like this? 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
February 3, 20188 yr @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!
February 5, 20188 yr Author 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 When you look at an indivdiul server it should be different:
February 5, 20188 yr 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: 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.
February 5, 20188 yr Author 1 hour ago, Seige said: Thanks for your response, I mean the "memory footprint" shown in the server overview. Mine looks like this: 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?
February 5, 20188 yr 43 minutes ago, clowrym said: Can you add a value to Xms and see if it makes a difference? Unfortunately, it makes no difference.
February 7, 20188 yr 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 TRANSMISSIONNO PORT UPDATER FOR THIS PROVIDERTransmission startup script complete.RTNETLINK answers: File existsWed Feb 7 04:29:36 2018 ERROR: Linux route add command failed: external program exited with error status: 2Wed 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?
February 7, 20188 yr 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 TRANSMISSIONCONFIGURING PORT FORWARDINGTransmission startup script complete.Wed Feb 7 17:41:53 2018 Initialization Sequence CompletedGot new port 36664 from PIAtransmission 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 serverChecking port...[2018-02-07 17:42:04.013] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server Edited February 7, 20188 yr by thedman added logs
February 7, 20188 yr Author Revert back to 1.19, there was an issue with the latest commit that killed access..... I believe he is working on a fix. https://github.com/haugene/docker-transmission-openvpn/issues/418 Edited February 7, 20188 yr by clowrym
February 7, 20188 yr 4 hours ago, clowrym said: Revert back to 1.19, there was an issue with the latest commit that killed access..... I believe he is working on a fix. https://github.com/haugene/docker-transmission-openvpn/issues/418 How exactly do I revert to that version in Unraid?
February 8, 20188 yr Author 15 hours ago, thedman said: How exactly do I revert to that version in Unraid? Change the tag:
February 8, 20188 yr Author Just now, thedman said: Thanks! Your welcome, These are the available tags https://hub.docker.com/r/haugene/transmission-openvpn/tags/https://hub.docker.com/r/haugene/transmission-openvpn/tags/
February 27, 20188 yr My VPN is not listed (ExpressVPN) in transmission_VPN, how can I use it ? Thank you in advance Edited February 27, 20188 yr by NY152
February 27, 20188 yr Author 15 minutes ago, NY152 said: My VPN is not listed (ExpressVPN) in transmission_VPN, how can I use it ? Thank you in advance you can make a request to have it added here: https://github.com/haugene/docker-transmission-openvpn
February 28, 20188 yr 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 March 4, 20188 yr by sosdk
March 16, 20188 yr 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 March 16, 20188 yr by NeoMatrixJR
March 20, 20188 yr Author 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
March 20, 20188 yr Author 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 March 20, 20188 yr by clowrym
April 1, 20188 yr I'm trying to run your Mineos-Node docker, and I'm having an issue that i ant seem to figure out. The docker is installed just fine, and I have the WebUI running, i can create a server, but not matter which profile i choose, the server will not start. I never get a /var/log/mineos.log, and the only log I can find is from the docker and it just states the following: USER_NAME not provided; defaulting to "mc" Created user: mc (uid: 1000) Generating Self-Signed SSL... Generating a 1024 bit RSA private key ..............++++++ ......++++++ writing new private key to '.tmpkey.pem' ----- writing RSA key 2018-03-31 20:27:55,370 CRIT Supervisor running as root (no user in config file) 2018-03-31 20:27:55,370 WARN Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing 2018-03-31 20:27:55,387 INFO RPC interface 'supervisor' initialized 2018-03-31 20:27:55,387 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-03-31 20:27:55,387 INFO supervisord started with pid 1 2018-03-31 20:27:56,389 INFO spawned: 'mineos' with pid 32 2018-03-31 20:27:57,403 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-03-31 20:29:14,930 CRIT reaped unknown pid 58) 2018-03-31 20:29:14,931 CRIT reaped unknown pid 59) 2018-03-31 20:30:16,101 CRIT reaped unknown pid 85) 2018-03-31 20:30:16,102 CRIT reaped unknown pid 86) 2018-03-31 20:33:25,428 CRIT reaped unknown pid 111) 2018-03-31 20:35:45,359 CRIT reaped unknown pid 146) 2018-03-31 20:35:45,359 CRIT reaped unknown pid 147) 2018-03-31 20:36:20,662 CRIT reaped unknown pid 172) 2018-03-31 20:36:20,662 CRIT reaped unknown pid 173) Every time I try to start the server, i get 2 - 3 more "CRIT reaped unknown pid" entries. Steps Ive taken thus far from reading other posts from everywhere I can find anything: adduser mc echo "mc:admin" | chpasswd chmod -R 777 /mnt/user/appdata/minecraft/ chown -R mc /mnt/user/appdata/minecraft/ chgrp -R 1000 /mnt/user/appdata/minecraft/ I have tried different profiles, from 1.7.10 to 1.12.2 vanilla, and even a few FTB options. It may be important to note that I have tried hexparrot's build too, and get the same issue. I'm flat out of ideas, do you have any? If it matters, I'm running Unraid 6.3.5 (cannot upgrade, later versions crash on my system) EDIT: found these logs, still not a lot of help here though. Says started, but its not. it immediately stops. mineos.auth.log mineos.log Edited April 2, 20188 yr by Rottonpeech
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.