tazire

I assume you are referring to the nextcloud config. The only line i have that refers to /nextcloud is on line 20 'overwritewebroot' => '/nextcloud', I know removing this will make accessing nextcloud through the unraid webui return. but at the same time its not my main issue. I just cant get the reverse proxy to work at all. I have tried the directions given and it results in my nextcloud being un-accessible through any means. EDIT Ok little update to this. outside the server it is working 100% as i want it. through letencrypt etc. only issue i have is when i connect while on network. The link I want works. but while on the network it bypasses letsencrypt, i assume that is normal? Also I have to put /nextcloud at the end of the address ie 192.168.1.18:4433/nextcloud. And this is the only way I can access it while on the network. So the unraid webgui doesnt work because of this. Also my android app wont find the server in the current setup which is an issue.

I'm having a lot of trouble getting this working in a reverse proxy for me. I am trying to get it working with xxx.duckdns.org/nextcloud. I have tried a few different way that were suggested throughout this forum... right now im at a point where when i type in 192.168.1.18:4433/nextcloud it will access nextcloud without going through the reverse proxy. Although I can no longer openWebUI through unraid anymore.... If i type in xxx.duckdns.org/nextcloud it just appears to redirect me to the local page and not actually going through the reverse proxy at all. I am fairly new to this and trying to learn as i go so please bare with me. Also my sonarr and couchpotato work properly through the reverse proxy. default.txt config.php

ok i figured this out... stupid me i tried to get this working in the past and was using a different default config.... i found it and fixed it... so at least i have a base working.

Tried unfortunately gives the exact same results.

I'm trying to get this working for the first time. I have installed the docker as directed but keep getting this error repeating nginx: [emerg] BIO_new_file("/config/keys/fullchain.pem") failed (SSL: error:02FFF002:system library:func(4095):No such file or directory:fopen('/config/keys/fullchain.pem', 'r') error:20FFF080:BIO routines:CRYPTO_internal:no such file) Currently i just want to get the docker working before i actually begin reverse proxy access to other containers etc. And here is the container params

ok well... as it turns out im still having issues since this accidental trigger. I still cant access certain shares since.... this is so strange. I cant figure out where to fix this issue...

having a minor issue. I was tidying up one of my shares of some junk files and in a mass delete set off the ransomware protection. Now all is fine that way... worked as advertised but i cant access the server at all from my pc now. I have no issue getting into it from my phone but even after resetting the SMB from read only I cant access it at all. Prob something simple but I just couldnt see it. EDIT A server reboot solved it. can disregard

Sorry thanks for that

just looking for a bit of help mapping a UD drive in windows 10. I have the drive working exactly as I would like and im just trying to map it in windows 10 for convenience. Its an external usb drive that I am using specifically for downloads. Its not the end of the world if I cant. I have included my settings. I tried \\SERVER\torrents to map it and also \\192.168.0.1\torrants but keep getting an enter credentials pop up.

im an idiot.... simple typo was causing the issue... sorted it out just going to check and make sure its writing to that disk now. fingers crossed thats it Yup thats exactly the issue. writing to the UD ssd now. Thanks

Just a question in relation to the transcode drive. I had a spare 120gb ssd lying around and im looking to use it specifically for transcoding. I'm trying to lighten the writes on my cache drives as much as i can... I have it mounted with unassigned devices and I'd like to now use it for the transcodes.... I created a container path pointing to it and put the corresponding path into plex but when monitoring it it doesnt appear to be using it at all. I also tried changing the TRANS_DIR container variable but that just broke it which i kinda expected. Any body know how I go about getting this working??

Sorry, thats what i meant. Thanks for the help. cheers

Ok i have everything done as described... funnily enough i found a step by step guide for plex dockers just after this. I am transcoding to my phone to try test if its actually transcoding to the new drive but I cant see any change in the amount of space its using up... I guess this would indicate that its not working??? at this point is this something i should be asking in the plex support rather than here?

Yes i am reading it and trying to find the appropriate posts. again as im not 100% confident with this yet im not sure im reading the right thing. from what im reading in relation to my issue... this appears to be the only thing i havent done "If you are running unRaid 6.2beta 20+, then you need to adjust your volume mappings mode (usually either RW or Read Only) to be RW:Slave or Read Only:Slave)"

ok well i have another parameter in the docker called /transcode and it is pointing to the mounted volume in UD. i assumed that was the correct approach? I have a feeling that i have the volume mapped correctly and it may be an issue with my plex docker

Sorry about this now but I wouldnt be 100% savy when it comes to all this. Do i need to passthrough the unassigned device in order to use it with the docker? i was just assuming the mounting did that for me.

Just curious if i have this done right. I have an SSD mounted with UD to specifically be used with plex as a transcoder drive. I then have a container path in plex pointing to the mounted drive. theoretically is this all i need to do to make the drive available in my docker? Just having a bit of trouble getting it to work how i want it. I'll go to the plex docker support if i at least have this much done right.

No need right after this i went and double checked the https port for unraid and i dunno what i had done before but the assigned port never took and defaulted back to 443. i reassigned it and all is back to normal for now. I will be trying to set up the reverse proxy again soon now that ive been reminded.

You're right im not. I was having issues getting it up and running correctly for me. I got it going with the intention of getting back to it. I just havent sat down to do it yet. I changed my unraid port for https but nextcloud still wont start...

I have done as stated above with the port change but now i have to specify the port when i want to connect to the nextcloud. essentially where xxx.duckdns.org used to work to connect I now have to put in xxx.duckdns.org:12345 in order to connect to the nextcloud... I'm guessing this isnt actually a nextcloud issue and something I can fix with my duckdns?

just a quick question.... i currently run my plex docker completely from my cache drive. As i understand this can cause high disk usage when all the meta data/ transcoding etc is done on the cache drive. I have read into the whole ram disk option but with 16gb I'm not sure i have the capacity for that to be viable. Would it be recommended to install another ssd as an unassigned device to run solely my plex meta data and transcoding to lower the load on my cache drive? I have 2 fairly new 1tb evos installed as the cache drives so i have no immediate concerns but i wouldnt like to burn them out with over use if i can help it.

Thats exactly what I have. I didnt realise this card didnt need to be connected what so ever. I had read that it needed to be connected for power reasons! obviously not. Thats spot on. Ill get on connecting this up tomorrow now. Thanks again.

The H97 should be UEFI, but I cant check right now. The toolset used for the Dell H310 has the necessary files for an EFI boot. Cant post a link as I'm on my mobile only. Thanks very much for this. The toolset had everything i needed. I didnt do it exactly as the read me said as I already had certain parts of the process completed in dos but its all up and running again. Just one last question... and i think i already know the answer to this one... I have an intel sas expander card.... it connects to a full pci e slot from what i can see... but im told this is just for power draw.. not a hope of this ever working in a pci slot im guessing??? Im fairly sure im gonna need a new mobo to accommodate it.

Is your BIOS up-to-date? It 100% is on the z87-k I even updated it after trying to load into the shell a few times. but its an old board and the latest bios is still old... The gigabyte board though doesnt appear to have a boot to efi shell on it. but it does have an override boot as you suggested earlier but i havent ever seen it populated. Its a cheap enough board... h97m-d3h or something i think. I havent updated that bios yet. not that it makes an awful lot of difference for the flash but the gigabyte board is the mobo on my server. I may just make the usb again... keep it as simple as i can with no other files other than the efi shell until i actually manage to get into the efi... I have followed a number of different how to's on this at this stage though.

This could be my issue but I set up my usb drive as a boot device using rufus. I have shellx64.efi then placed on the drive. It doesnt seem to appear in the override boot section on the gigabyte modo. On the asus one I just cant get past the secure boot at all... I have it set to other os and states the secure boot is disabled but i still get the secure boot issue. You could be right that I havent got the usb set up right. But on the other hand I have been able to boot into the freedos thats loaded onto it. and i can see all the files using the dir command etc...