tazire

I'm starting to run into a strange issue. I can no longer play media on the Web browser. I haven't tested this fully as I'm not at home. But I literally went through a big upgrade. Now a Ryzen 7 1700 with 32gb of ram and a p4000 I have the whole lot up and running and the transcoding works as best it can using the p4000. But when I try play anything with the we player I get this error in the logs. usr/lib/plexmediaserver/Plex DLNA Server: relocation error: /usr/lib64/libssl.so.1.0.0: symbol ENGINE_init version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference Just FYI I have changed from transcoding to an SSD to ram. I'm not sure if that has anything to do with it. Sorry I'm not at home to give full logs right now.

Im having a RAM issue with my plexpass docker atm. Basically RAM usage just keeps going up until it uses every last bit of it. I have now had to restart the docker once a day to ensure it doesnt reach 100% usage. I knew about the issues with sonarr and radarr etc and although the usage for these can be irritating they dont hog the RAM nearly as much or a quickly as plexpass has started to. Any idea what may be causing this? And what is needed to possibly diagnose this issue.

This.... fair play thanks for that. deleted and re added my account and all is working as it should be.

ok i went in through putty rather than the console and got the following result root@553d247f5e00:/$ find /config/nginx -name \*.conf -exec grep -H client_max_body_size {} \; /config/nginx/nginx.conf: client_max_body_size 0; appears that its not finding every instance in every file. I know it is also in the proxy.conf and the nextcloud.conf but again each one is set to 0.

Thanks for the help. i just tried that command and i got this issue find: -exec requires an argument

ive checked all the .conf files I could find and they all seem to say client_max_body_size 0. I just ment that the proxy.conf is the only place I found it set to 10M but I changed it and still no joy. But again as i said it only seems to effect the windows client. I have updated to the latest client just to see if that helped but no joy ATM.

Getting a very strange issue atm. I have files that I am trying to upload from my desktop using the synced folder. pics and videos mostly. With all the videos I get the error 413 request entity too large. I understand this relates to a client_max_body_size variable somewhere being set too small. So i went through all the .conf files and replaced the proxy.conf variable to 0. This is the only one that I could find with the variable set to 10M. There is also a client_body_buffer_size 16k but im not sure if that effects it at all? This only occurs with the synced folder in windows. I can access the webui and upload that way just fine. Thats the thing I find strange. Any ideas?

Ok it all seems to have sorted itself out once i re enabled the default encryption module. I havent ventured back into getting the end to end encryption working but everything is back as it should be with the default module enabled. folder and the files can be edited now as well. I havent tried re installing the stable release of the android app yet though.

In relation to the android app there is some issue with the play store storing some residual files also. It was causing the same issue on the new phone. I ended up going with the beta app just to get myself up and running. Only problem is im not sure if this will auto update now. Probably not a question for this forum really. but your info so far was helpful. In relation to the random info. I couldnt edit it after I edited it with CAConfig either. I actually cant do anything with the php folder at all.

yea it shows false... also when i put /status.php in the address bar here is the output {"installed":true,"maintenance":false,"needsDbUpgrade":false,"version":"14.0.3.0","versionstring":"14.0.3","edition":"","productname":"Nextcloud"} Since this issue i uninstalled the nextcloud app and reinstalled it and strangely enough it just crashes on install and everytime i try to open the app after it crashes. and i get the same result each time i uninstall and reinstall. I might just shelve this until monday as i have a new phone arriving then and a fully fresh install might be able to shed a bit more light on it... possibly something strange in the config of the app on my phone thats just lingering there. As i said everything else seems to be working. Well other than being able to get the encryption working. EDIT Just a random bit of information I have found while messing with this. I had the memory_limit issue where i had to put memory_limit 512M in the php-local file but I couldnt edit this using notepad++ as i didnt have permissions. It appears that the permissions of the php folder and contents have changed. or is that just standard? I managed to edit it using the CA config editor. I have full access to all other folders in the nextcloud appdata. Might be nothing but just found it strange.

I am having a strange issue with the android app atm. I currently keeps getting upload failures with the android app only saying that the server is in maintenance mode. I tried puttying in and doing the following commands docker exec -it nextcloud bash sudo -uabc php7 /config/www/nextcloud/occ maintenance:mode --off but it says that the server isnt in maintenance mode. Just to inform you i had been trying to the the end to end encryption up and running just before this started to occur but gave up and removed all the encryption apps. I now have the following under encryption settings No encryption module loaded, please enable an encryption module in the app menu. and i cant untick the encryption box. Any help?? EDIT have full access using the windows app and webgui. just appears to be an app issue.

Finding this super slow atm. But at least its stable for me. Duplicati was just a nightmare for me. I am currently running at about ~150kbps on a gigabit network to a local storage. It could be that the external storage is an external hdd attached to the router and the router is just struggling perhaps. Actually considering investing in going pfsense rather than the RT-AC68u i currently have. Final question is if/when i buy the licence is the server licence required for the unraid setup or is a personal licence sufficient?

Im not sure how this is running for anyone else but i am finding it very unstable atm. I go it running and completed a backup to a b2 storage location but with a few errors reported and after a couple of retries. I have a second backup to an external device attached to my router and no matter what i do it just will not finish the back up. but this seems to be caused by duplicati crashing. the latest crash ment i couldnt restart, stop or delete the docker. Im currently stuck trying to get the dam thing to shut down using putty.. but no joy atm. Theses are the last entries in the log before it stopped working. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. EDIT Ended up having to hard reset the server to get back to a somewhat workable situation with this unfortunately.

I'm having an issue with the docker not starting for me. The log for the docker itself wasnt showing anything but when i go into the unraid log the following appears Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered blocking state Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered disabled state Oct 20 12:06:19 SERVER kernel: device veth9567ac9 entered promiscuous mode Oct 20 12:06:19 SERVER kernel: IPv6: ADDRCONF(NETDEV_UP): veth9567ac9: link is not ready Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered blocking state Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered forwarding state Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered disabled state Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered disabled state Oct 20 12:06:19 SERVER kernel: device veth9567ac9 left promiscuous mode Oct 20 12:06:19 SERVER kernel: docker0: port 13(veth9567ac9) entered disabled state Any ideas? Had been working up until I had to force a reboot due to a mover hang. EDIT fixed itself after another reboot.

ah very good. I guess on the one hand the majority of the hard drives are going to be read only after the contents is added. Also i am formatting each drive so fragmentation shouldnt be an issue. Ill look into that hard limit when im done with the process. cheers for the response.

Thanks for the info. I have shut off everything that might add or move files on the array. Plex will stay active but it shouldnt change any drive. One more question. As i said earlier im using this to encrypt my drives. When im moving files to empty drives I have a few drives that are 100% full, save for about 500mb. Im not sure if this is over filling the hard drives if i wanted to defrag etc. or when im done is there a way to balance the data over the entirety of the array? Or is this totally fine to leave as is!

Sorry just a quick question.. is it best practice to turn off dockers and vms when using this? just I am using it to encrypt a large existing array and as you can imagine it will take quiet some time. I have a few ppl who use the services regularly and am curious if having dockers running will cause any issues. Sorry if this is already answered I couldnt find it when i searched and googled it.

anyone using this having trouble with the indexers? For some reason it just constantly says indexers unavailable... i have gone in and tested the connection to them and it will test just fine but when i go to search it will give an error that 4 of 5 indexers arent working. i have double checked each indexer in radarr and sonarr and they work just fine. I realise this isnt really an issue for the docker setup as such but just curious if anyone had similar issues and resolved it. Cant seem to find any relevant info when i google the issue.

Ah thanks for the update. should have checked. cheers Is there any EU server that ppl would recommend now? from what i can see swedish server has best throughput?

I keep getting the following error when restarting the docker. 2018-08-22 11:16:03,661 DEBG 'start-script' stdout output:[warn] Response code 000 from curl != 2xx[warn] Exit code 7 from curl != 0[info] 8 retries left[info] Retrying in 10 secs... I am a PIA user and i connect to the netherlands server which i believe already has port forwarding on it. Is a reinstall required to fix this?

Just curious about back ups for the nextcloud server. Not sure if this is the best place to post this but basically i want to be able to back up the full server, database and data to an external HDD. Whats the best way to do this? IS there another docker thats worth installing to do this automatically?

Ok well i guess the issue has to be in the nextcloud file because it was running fine without it. So ill just go back and start from scratch with that.. EDIT Just went back to all the settings that up until i started trying to get nextcloud to work had worked just fine.... broken... same issue as mentioned above. No idea whats going on now 2nd EDIT.. Completely baffled now. I just did a fresh install of letsencrypt with no new config files what so ever and i am getting the above error. no idea whats going on atm...

i tried it both ways. ideally i wanted mynextcloud.duckdns.org but i also want to use tazire.duckdns.org/container for my other dockers

Yea it seems not matter which way i try im getting that error atm.

ah... funny how you just don't see whats right in front of your face... duh.... no my unraids ip isn't that! thanks. I sorted out the extension also. but im still getting the same error as above! EDIT Just one other thing that might be the issue. I have one domain with sub-folders for all my other dockers ie. sample.duckdns.org/ombi Where as i have nextcloud.duckdns.org as my nextcloud domain. Could this be the cause of this issue? I tried nextcloud.sample.duckdns.org before and just couldnt get it working. so i updated the letsencrypt perams as shown