Wob76

Hi, I have started getting heaps of black results, more than actual results, i have timeout set to 60seconds, have tried both beta and 0.3.4 without much luck. changing the timeout to 30 seconds don't seem to stick for some reason, it just reverts to 60, i can set it to 20. I have a set server, I have tried multiple servers without any luck. Any ideas? Thanks, Wob

Hi, First off thanks to aptalca for the container, I installed yesterday and it's working a treat. I replaced the apache reverse proxy I was using, having it auto handle SSL is great. I have it doing reverse proxy for a few things, I had a bit of a mission getting it to talk to binhex's rutorrnetvpn docker, so thought I would add my config here to save anyone else the time doing it later. I used aptalca's config examples as my starting point, and I also had to disable php for rutorrent (like aptalca mentioned for plexwatch). I didn't want to modify the rutorrent config, so I have this docker doing a url rewrite. I am also using a different username in rutorrent, so I added a auth setting to authenticate between this docker and rutorrent, so I only need to authenticate with this docker using it's username and password. This is the entry in the site-confs/default location /rutorrent { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; proxy_set_header Authorization "Basic ####INSERT BASE64 HASH####"; rewrite ^/rutorrent(/.*)$ $1 break; include /config/nginx/proxy.conf; proxy_pass http://192.168.0.250:9080/; } Oh, to generate your BASE64 Hash you can use an online encoders such as (https://www.base64encode.org/) So take username:passoword (using your username and password as defined in rutorrent) and encore and you will get something like "dXNlcm5hbWU6cGFzc3dvcmQ=" and that line will look like; proxy_set_header Authorization "Basic dXNlcm5hbWU6cGFzc3dvcmQ="; Personally I would ensure the password is unique, if someone gets your hash they can decode it. Hope that helps someone. Wob

Hi, My log file "other_vhosts_access.log" is rather large 427Mb at the moment, the settings enable\disable it are not in the config folder, nor any of the logrotate settings. Could the docker be modified to expose settings to help reduce log files, my preference would be to have it included in logrotate. Thanks, Wob

Hi binhex, Is there any way to set a rotation or flushing of the access.log, mine is currently 96Mb, mostly just logs from web browsers left open and it refreshing history data, etc. Thanks, Wob

Thanks... I will update and fix soon. I"m just checking this issue right now, are you guys setting the TZ variable? Hi, I did set it and it had no effect. Wob Sent from my SM-G900I using Tapatalk

Just playing a little more, I noticed on my box that the v0.3.1 script does exist, if I select that in the GUI I just get no result.

Hi dmacias, I just wanted to say thanks for the latest update, I have mine set to use the beta with a manual server and a timeout of 60 seconds, no more blank results. Thanks, Wob

Thanks dmacias, Your solutions sound like they will do the trick, as I mentioned I mainly use it to test for peak speed dips, and it does a great job at that, just the blank results that are putting me out, so if there could be a check or retry for that it would be great. Thanks, Wob

Hi, Thanks for the great plugin, it is very handy. I have a slight "bug\issue" If I leave my server selection on auto I get poor speed results around 30Mbit/s Down and 3-4Mbit/s up using server (UBC Web Design (Ballarat)). But If I manually select a different server I get around my actual speed connections. I put this down to the server it is landing on, if I manually run speedtest-xml I see the same results. If I run speedtest-cli I get a server (Telstra (Melbourne)) and speeds close to max (91-93 and 34). However if I manually run speedtest-linux I get a different server (Melbourne (Telstra)) and speeds close to max. So there seems to be a change in logic of server selection with speedtest-xml. I am not too worried about gettting a MAX reading, I really run it too see if I get any peak speed drops, so manually selecting the server is OK. But the issue I have then is that I seem to get more blank results back, than if I leave it on auto. I am not sure why it is failing (not much in the logs) but I know my connection is still active at the time of the test, I have other things running to detect dropouts. Is it possible that the -xml could have its server selection tweaked, or if when selecting manual you can have a backup server that is used if no result is returned? Or even the ability to black list some servers? Blank Result Log: Jun 3 00:00:01 TheBox speedtest: Internet bandwidth test started Jun 3 00:00:12 TheBox speedtest: Host: Jun 3 00:00:12 TheBox speedtest: Jun 3 00:00:12 TheBox speedtest: Internet bandwidth test completed Also, when I select "manual" on the settings page, I seem to get the same servers listed multiple times, I can't tell if they are different, name and distance is the same, maybe if it returned the server number as well so we could identify them? Thanks again, Wob Edit: Just some further info, with the plugin on auto it states it is using ping to pick a server, but the ping results are much higher than when I manually select a different server. Auto Jun 3 12:37:54 TheBox speedtest: Internet bandwidth test started Jun 3 12:42:30 TheBox speedtest: Host: UBC Web Design (Ballarat) [151.03 km] Jun 3 12:42:30 TheBox speedtest: Ping: 49.018 ms, Download: 30.90 Mbit/s, Upload: 3.65 Mbit/s Jun 3 12:42:30 TheBox speedtest: Internet bandwidth test completed Manual Jun 3 13:02:17 TheBox speedtest: Internet bandwidth test started Jun 3 13:02:46 TheBox speedtest: Host: AARNet (Melbourne) [225.60 km] Jun 3 13:02:46 TheBox speedtest: Ping: 32.289 ms, Download: 91.89 Mbit/s, Upload: 35.79 Mbit/s Jun 3 13:02:46 TheBox speedtest: Internet bandwidth test completed

Hi hurricanehrndz, Any ideas re my post above? Should I be directing the query to the emby forum? Thanks, Wob

Hi, Do you need to turn off the auto update feature within Jackett? It is on by default, I didn't touch it, but a few days ago my container crashed, looking at the logs it appears this was after it attempted to auto update. On a side note, are there an options in unraid to have dockers restart or update on a schedule? Or do I need to look at cron jobs? The new plugins autoupdate seems to be working a treat, something similar for dockers would be nice. Thanks, Wob

Not sure if I should ask this here or over on the Emby forums, I'm having issue with times in Emby. The container time and timezone seem to be fine if I exec into it. Wed Jun 1 15:15:16 AEST 2016 But the logs are wrong, and the scheduled tasks fire off at the wrong times. End of the Log at the moment. 2016-06-01 05:11:09.6774 Info TaskManager: ExecuteQueuedTasks I'm sure I am missing a setting somewhere, just can't work out where. Thanks, Wob Edit: Just some further testing, I tried adding TZ="Australia/NSW" then "Australia/Sydney" with no effect. I noticed in the container that localtime is pointing to UTC, should this change? lrwxrwxrwx 1 root root 27 May 8 00:56 /etc/localtime -> /usr/share/zoneinfo/Etc/UTC I also tried unticking the "bind time" option, but it seems to revert back anyway. My unraid box is using the correct localtime. "AEST-10AEDT,M10.1.0,M4.1.0/3" Wob

not as far as i know, no, i just did a quick test, loaded up a torrent from a public index site and i can see seed/peer counts increasing from a udp tracker, so looks to be working, check your rtorrent.rc file and make sure udp is enabled. Yeah I did do that, I'll do some further digging. Thanks, Wob Sent from my SM-G900I using Tapatalk

I'm with binhex on that, that icon is related to the port checker, which should be checking your listening port, can you screenshot your port setting page? Binhex, do you have any issues with upd trackers? Like I posted. Wob Sent from my SM-G900I using Tapatalk

Hi Myk, Are you talking about the port checker down the bottom? That should be checking whatever port you are using to connect externally, and you need to ensure you have allowed that via your firewall (if you have VPN disabled, which you had said you were doing). If the port checker is not green then your upload speed will be poor. Port 6881 is the port for DHT, I have it disabled as most private tracker sites frown upon it's use. I don't think there is any check for it on the bottom though, so unless you have set your Listening port to the same port number it shouldn't set of any alarms, and I don't think it would be best practice to use a port that low for your listening port. Cheers, Wob

Hi (again), Is anyone having problems with UDP trackers? all my HTTP trackers are working a treat, but all the udp trackers come back with "Tracker: [unable to connect to UDP tracker.]" I don't have many UDP trackers, so haven't noticed it till now, everything else is running a treat a the moment, going out via PIA's Romanian server. Regards, Wob

aptalca: Thanks for the reply, so are you saying you don't need to modify for each new container? I currently need to add a new subpath to port mapping for each new container I wish to have internet facing. Thanks, Wob

But do either have docker-gen, it enables automation of the reverse proxy config using docker API. I am yet to try it, the linuxserver.io gave it container of the month, so I was hoping a unraid template might follow.

Any update on this, docker-gen sounds very interesting. I am currently using the linuxserver.io Apache server for reverse proxy, but some automation of new containter sounds great. There is a docker with it and nginx combined (https://hub.docker.com/r/jwilder/nginx-proxy/) would be interested if anyone has this running in unraid? Thanks, Wob

Not sure how I missed that Thanks, looks good.

Hi binhex, Any thoughts on this? Thanks, Wob

Is anyone else seeing the "Welcome Emby Tester" message since the last update? I am running emby/embyserver:latest not the dev branch, so not sure why I am seeing this. I wasn't too worried to start with, just closed the dialogue and everything seemed OK, but I am also seeing slow downs since the update. I am seeing "Version 3.0.5934.0" in the settings. Is it possible to roll back versions of emby, or will that mess with the database? Thanks, Wob

Hi binhex, I am still having some issues with the multi-user environment. I use authentication on my reverse proxy, and every now and then it passes that auth on to rutorrent, and even though and account doesn't exist with that name it creates a folder under /share/users/ with that username and logs me in, and this messes with ratio's etc as discussed previously. I would like to disable multiuser by adding $forbidUserSettings = false; to the config.php, but you currently don't expose that outside the container. Is there any chance that this will be migrated\linked to the /config file in the future? Or alternatively can I request that the above variable be made the default, since for proper multiuser support requires separate rtorrent installs and scgi ports for each user. (As described here https://github.com/Novik/ruTorrent/wiki/Config) Thanks, Wob

After having the container running for months, I started having the 2 accounts issue, some digging found a solution, change the network mode from bridge to host.

Thanks for the response, I'll do some testing soon and see what I can find.