bobokun
-
Posts
224 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bobokun
-
-
On 9/23/2017 at 2:09 AM, mikefallen said:
Having same issue can't find forum post your talking about do you mind detailing how you fixed it would be greatly appreciated!
Found a fix
Delete codecs folder in appdata:
\appdata\plex\Library\Application Support\Plex Media Server\Codecs
Restart the docker image and it fixes the issue
Thank you for this! I had the exact same issue and deleting the Codecs folder solved everything.
-
18 hours ago, JohanSF said:
Since the mover skips files that are used by rtorrent I found it necessary to close down rtorrent everytime I run the mover.
Is it possible to write script or similar that properly stops the rutorrent docker when the mover is run (and waits for the docker to stop before starting the mover) and then starts when the mover has finished? i.e. having stop-start of a docker (but only if it is running) triggered by the mover starting.If you guys use a better solution, please share.
I have no idea how to do this as I am new to the platform and extremely basic at linux, so any help is appreciated.
Edit: Maybe someone can make this happen with the CA User Script Plugin, or a script that is then added to \flash\config\plugins\dynamix\mover.cron? I also found out that the command "sudo mover" works, but then I can't use rely on the invoke mover button in the webgui. -
I also tried to get this to work as well but keep getting error in my logs. Not sure why it's using port 80 even though I specified to use a different port.
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) -
@balloob are there any plans on upgrading the docker container to Hass.io?
-
6 hours ago, assassinmunky said:
that should not be necessary. anything under your specific duckdns subdomain is already owned by you.
lets say your subdomain is "mydomain":
www.mydomain.duckdns.org
tor.mydomain.duckdns.org
blah.mydomain.duckdns.org
These are all already owned by you.
I'm not familiar with the duckdns/letsencrypt setup. Is this all in one docker container? or do you have a separate container for duckdns and a separate container for letsencrypt?
4 hours ago, aptalca said:Url should be the top domain that you have control over, ie. test.duckdns.org
Then the subdomains would be tor and whatever else you likeThank you both! I've got it working now by changing the domain to "test.duckdns.org" rather than just duckdns.org. Now everything is working as expected
-
1 hour ago, assassinmunky said:
this looks good, means your nginx reverse proxy is working as expected. Now you just have to fix your letsencrypt cert to allow for the new subdomain.
Edit your letsencrypt docker container and "tor" to the list of subdomains, see attachment
Hmm, seems like a problem with duckdns. Using the example test.duckdns.org, when setting up duckdns with letsencrypt the Domain name is (duckdns.org) and the Subdomains are (test). Adding tor to the subdomains will give me an error with letsencrypt logs.
Domain: tor.duckdns.org Type: Connection Detail: TimeoutI've tried adding in my subdomains (test,test.tor) but it didn't work either. I might need to go into the duckdns website and create a subdomain through there and it should work.
-
2 hours ago, assassinmunky said:
So the subdomain will be something like "tor.test.duckdns.org", not a new/separate duckdns.org subdomain. I use dyndns.info and adding a another subdomain to mydomain.dyndns.info doesnt require any additional configuration on the dyndns.info site, so i assume its the same for duckdns.org. On the letsencrypt docker, you will need to add "tor" to the list of subdomains, and restart the container.
The nginx config i pasted earlier goes on the letsncrypt docker container, not the rutorrect docker. You will need to restart the container after you edit site-enabled/default
Sorry for so many questions, I'm having some issues with my config. Do I add the nginx config that you pasted into "appdata\letsencrypt\nginx\site-confs\default"
config file or do I create a new one calling it tor.test.duckdns.org? I've tried to add it at the bottom of the default one so above I have something that looks like this...
server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name _; ... } server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name tor.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES12 8-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-R SA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA25 6:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA- DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; ... }But when trying to visit the webpage I'm getting this error. I've restarted my letsencrypt docker as well as rutorrent
-
1 hour ago, assassinmunky said:
Yes, it's possible. you need to use the sub domain -- the url/path doesn't work here.
this is my nginx config for "tor.mydomain.com"
server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name tor.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES12 8-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-R SA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA25 6:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA- DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:10080; # change this to your rutorrent ip/port } }So would I need to create a separate duckdns subdomain for my rutorrent? For example right now my I'm using test.duckdns.org and to access my plex or ombi I would go to test.duckdns.org/plex or test.duckdns.org/ombi but I theres no way to get test.duckdns.org/rutorrent to work I would need to create a separate subdomain test2.duckdns.org in order to point towards rutorrent. Please correct me if I'm misunderstanding...Also is that nginx config in your letsencrpyt docker or is it your rutorrent docker?
-
@truetype did you ever get this to work?
-
1 hour ago, kizer said:
Check your Cache Drive. Your settings and well literally everything else lives on the Cache drive so make sure its up and running.
Is there any way to change the header link for the WebUI? For example if you add the header for a docker container like Ombi the link now changes to http://[IP]:3579/ombi but in the webUI it still points to http://[IP]:3579. Any easy way to change it?
-
Looking to install a music bot to stream music on Discord.
Can anyone make a template for this? I believe that it already has a docker container for it
https://github.com/Just-Some-Bots/MusicBot
-
does anyone have permission issues when accessing usershares via smb? I can't delete files that are created by automove plugin in rutorrent. I've already commented out the system.umask.set=022 in rtorrent.rc file.
-
1
-
-
There was an update that released today on sonarr. Can I update this through Sonarr or will I need to wait until the Docker container updates Sonarr
-
Has anyone managed to successfully get rutorrent working with reverse proxy (following the letsencrypt and duckdns guide)?? I've been trying to figure out how to get it working but nothing seems to work properly.
-
exactly the same thing I had the other day. try doing this
-
It worked. Thank you
-
On 7/24/2017 at 5:40 PM, Squid said:
Alternatively, you can disable mover from running automatically as per the directions here: https://forums.lime-technology.com/topic/48707-additional-scripts-for-userscripts-plugin/#comment-483789 and then use user scripts to manage everything (Note that this is a hack, and any changes to a setting in the scheduler will undo this change)
docker stop rutorrent mover docker start rutorrent
Although it would probably be good to specify the time to wait for a graceful shutdown of rutorrent before killing it:
docker stop -t 60 rutorrent
so that rutorrent won't have to recheck all of the files when it starts back up.
I noticed that the script doesn't seem to execute the mover command.
Do you know what the full path of mover is?
This is my script:
#!/bin/bash
echo "Stopping rutorrent"
docker stop ----time=60 rutorrent
echo "executing mover"
mover
echo "Mover Complete. Starting Rutorrent docker"
docker start rutorrent
echo "Successfully started rutorrent"
Output Log:
Stopping rutorrent rutorrent executing mover /tmp/user.scripts/tmpScripts/mover (Stopping dockers)/script: line 5: mover: command not found Mover Complete. Starting Rutorrent docker rutorrent Successfully started rutorrent -
4 hours ago, Frank1940 said:
You might try installing the 'Tips and Tweaks' plugin. Then on the 'Tweaks' tab, turn on the 'Help' (button in the Header menu). Now set the "Disk Cache 'vm.dirty_background_ratio' (%):" and the " Disk Cache 'vm.dirty_ratio' (%): " to the the suggested Streaming and VM settings. (The default are probably OK for systems with less than a 2GB of RAM but a bit excessive for what most of us have in our servers! Plus, these defaults were setup originally to increase the perceived responsiveness of system where the user is actively working on the system desktop.)
Thanks! I installed the plugin and changed the default values. Hopefully this fixes it
-
I noticed my server was lagging very heavily suddenly today and I couldn't access any of my dockers or even browse usershares. Even logging into SSH was very laggy. I tried to stop all dockers but the system was hanging. I managed to stop the array after waiting what felt like 30minutes. After stopping the array the system was quick to respond again, however when scanning fix common problems it showed some errors (See below). Please see the attached diagnostics
-
Passed another round of preclear and values didn't change
thanks for everyone's support!
-
20 minutes ago, trurl said:
Do you really need its capacity right now? If not, I would just leave it out and go for newer bigger later on as bjp999 says.
Adding a disk just because you have it isn't really a good idea. More disks means more opportunities for problems. If you don't need the space don't add a disk.
In that case should I just leave it as an unassigned disk not on the array and use it to backup important appdata and documents? Would I be able to create a usershare that is on the unassigned disk or is the only way to access the disk directly through /mnt/disk/
-
10 minutes ago, bjp999 said:
Since it is not in the array yet - do a preclear on it. Let's see what the attributes show afterwards.
It's passed two cycles of preclear (results are in the first post)
That's why I was wondering if it was safe to add to my array. I think it should be fine now that the SMART status has changed with no errors
-
It isn't a smart report for a different disk. If you compare the values from the post with the one from the first post all the values are the same except the offline uncorrectable. The notification message I got was that the offline uncorrectable value changed in the SMART status. Not sure what that "undefined undefined " overlay is but its a notification I just noticed and cleared it...Maybe because I was browsing using mobile when I took the screenshot? Not sure. I haven't added this drive to the array yet. So please correct me if I'm wrong. I should add the device to the array first, let it do a parity check 3 times without corrections to the parity. Is the only way to do that is clicking on the check button 3 times (while leaving the write corrections to parity unchecked) or can I run it three times consecutively. Each parity check takes quite a while to do so it might take a couple days to complete.
-
15 minutes ago, bjp999 said:
"Fails" is a strong term. Drives rarely fail. They are not light light bulbs and other electronics, which will just refuse to turn on when they break. Drives tend to (but not always) show some SMART attribute anomalies. If left untreated to they tend to do nastier things like cause read errors, and/or occasionally start reporting invalid data. It is VERY rare that a drive actually "breaks" to the point it won't power up or be recognized by a controller.
As an aside - in some ways unRAID would work much better if drives DID fail like light bulbs. Poof - drive is dead. Replace / rebuild it. It is the act and diagnosis of failing and that causes so many problems!
If you are attentive (and I think plugins like find common problems help with this), you see the SMART problems and act on them, preemptively addressing problems before the drive starts spewing garbage which can will mess up parity and cause even single disk recovery to be imperfect. When I get a problem like yours, I will run a few non-correcting parity checks. If I can get through 3 of them in a row and SMART problems get no worse, I'll trust the drive. But if I run 4-5 and they keep coming, or worse I start getting parity errors, it is time to replace the drive.
Something interesting happened which I did not know could happen. I got a notification for that same drive today which showed the error disappeared in the SMART report.
[Support] Linuxserver.io - Ombi
in Docker Containers
Posted
What's the easiest way to transition to v3? Did you have to start from scratch or was there an easy way to keep your settings