leejbarker

It did this to me.... I noticed there was an update for File Browser, updated that and now it works fine.

Setting my connect to Bridge and giving it a port has fixed my external access problems... FYI

Worth adding that to connect you'd have to go {yourip}:{portyourusing}/files For example, my IP is 192.168.0.10, I've set it to port 8085.. So I use; 192.168.0.10:8085/files/ You can change the default WEB UI address on the docker settings under the advanced view.

Further question... I can't get this to work when I access the NAS from a WAN connection via OpenVPN... Is there anything I can do to make it work... I am attempting to access it the same way I would from the LAN connection....

It's working suddenly.... Haven't got a clue how or why!! Thank you

Going to the web browser says This site can’t be reached 192.168.0.25 took too long to respond. The log states; 2019/03/24 08:37:09 Listening on [::]:80 2019/03/24 08:37:09 Using config file: /.filebrowser.json

Attached is my current config, but when I hit the WEB UI it just says site can not be reached.

Hi knex666... Don't suppose you could provide a little bit more detailed install / conf instructions for the novice pls? No worries if not! Thanks Lee

@Squid does it matter if I just change the built-in schedule to Monthly rather than changing the share.cfg file?

Ok, out of interest - did the sleep command work at all

How did this work for you? I think the to turn TW off you need to set it to md_write_method 0

Yes that works perfectly.. no worries

Hi, I noticed that it has already been discussed combining Turbo Write and Threshold Mover Script. I can't get the damn thing to work, it just seems to freeze my system for a while. Could someone post the script.txt file to make sure I'm not being an idiot? Thanks

Hi, Hoping someone can give me a basics lesson... I'm used to using get_iplayer on windows via CMD. I've putty'd in to my NAS but can't find the get_iplayer anywhere... Am I missing something? Is this not possible?

I haven't been getting any errors for a while now. I bought some more memory and that's the only real change I've made.

I’ve just finished testing and so far no errors with everything installed. My testing process is outlined below. I pulled the last diagnostic that I posted, uninstalled everything and restarted. Then I added just Plex and the Community Apps Store, added Plex Media - No errors Then I added PlexPy to the mix - No errors Then I added the Dynamix plugins one by one - No errors. So, I’m at a loss for what was causing the issues. My best guess is that there is something wrong either the USB stick or my memory. I’ve ran several passes of Memtest and that passed, so I suspect that the USB stick is doing something funny whilst loading to RAM at the start. I’ll post another update on in a few days time to confirm everything is behaving and that this was just one of those odd issues. I have noticed that the Plex Media Scanner seems to be taking much longer than usual, but I can live with that. Thank you so much for taking the time to help me. Diagnostic attached. nas-diagnostics-20170310-1034.zip

So I woke up to a ton of errors, diagnostics attached. I'm doing the test now, so far I haven't had one error throw up running just Plex (which is essential) so I'm happy about that. Will post fully when I've finished. nas-diagnostics-20170310-0851.zip

Thank you for your help, I really appreciate it. I will try this in the morning. Interestingly, I have been out all evening and my server hasn't thrown any errors up. I got home and added some Media Files to the Video Share. I then ran the plex library update and it's thrown a number of errors up. Diagnostics attached. nas-diagnostics-20170310-0019.zip

How do you do that?

As Requested nas-diagnostics-20170309-1719.zip

And just these Mar 9 06:51:31 Tower kernel: Plex Media Scan[3117]: segfault at 0 ip (null) sp 00002b65421ff8d8 error 14 in Plex Media Scanner[400000+42e000] Mar 9 06:51:31 Tower kernel: traps: Plex Media Scan[3099] general protection ip:2b653c864552 sp:7fff318dc750 error:0

Had these not long after too Mar 9 06:10:03 Tower kernel: kvm: already loaded the other module Mar 9 06:10:16 Tower kernel: kvm: already loaded the other module Mar 9 06:42:59 Tower emhttp: err: sendOutput: fork failed Mar 9 06:43:02 Tower root: Mar 9 06:43:02 Tower root: mmap() failed: [12] Cannot allocate memory Mar 9 06:43:02 Tower root: Mar 9 06:43:02 Tower root: Can't initialize heap: [12] Cannot allocate memory Mar 9 06:43:02 Tower kernel: dockerconfig.ph[24009]: segfault at 0 ip 00000000005f42ad sp 00007fff745f4060 error 4 in php[400000+724000] Mar 9 06:43:02 Tower emhttp: err: _shcmd: system: Cannot allocate memory Mar 9 06:43:02 Tower emhttp: err: _shcmd: system: Cannot allocate memory Mar 9 06:43:10 Tower emhttp: err: sendOutput: fork failed Mar 9 06:43:10 Tower emhttp: err: sendOutput: fork failed Mar 9 06:43:11 Tower emhttp: err: sendOutput: fork failed

Does anyone have any idea what this means, what I should do and do I need to worry? Mar 9 06:09:48 Tower kernel: php[25428]: segfault at 0 ip 00000000005f42ad sp 00007ffeb4615e90 error 4 in php[400000+724000] I've ran memtest and check disk on the USB as suggested in other forum posts I've read. No faults detected. It seems to throw it up when switching between menu tabs on the WebGui. I am adding Media to my Plex Libary too, so that could have something to do with it.

Ok, I've fixed my error. I had previously set my Transcoding folder to use RAM instead of the Cache. I looked through the Plex Server log and saw there was a permission error on the Transcoding part. I changed the Transcoding folder to the Cache / Appdata folder and it's working normally again.

I've just started using Plex Docker on Unraid. Plex version 1.4.3.3433. Upon adding fresh media everything works fine. However, when I restart the server, the media won't play. It is still recognised by Plex (showing in the library), but simply won't play. I try restarting the docker etc but that still doesn't work. Interestingly, everything seemed to be working fine in LimeTech version of Plex Docker, which I think is 1.3 ****, so might be a fault on the Plex end. Does anyone have any suggestions?