Dent_

Been trying to get this docker going again and thought I would point out that the POSTGRES_PORT key has a space at the begining that causes startup to ignore port #. It does not appear to be a problem if you are using the default port but, if like me you are using a non default port number it ignores and uses default of 5432.

I had to add a variable in the mealie docker settings for BASE_URL with the url used to get to my instance.

Not right now. According to Photoprisms project roadmap multi user support is now in sponsored development but no current ETA that I have found.

Thanks, I figured it was probably a variable I missed. Didn't think about amount of php processes to DB connections. As for the increase in connections I did increase the shared_buffers memory as well as the worker and maintenance variables based on your template and explanation at the same time. Thanks again for your guide.

Thanks for this. Great help for those of us who like to play but do not have a lot of exp with the deeper end of servers. I have not used all the guides(yet) but got my way through some of them. I do have a couple questions. You said you have a larger Nextcloud server on your postgres DB. Did you have to substantially increase the max_connections? Once I installed max_connections was set to 100 (default). My nextcloud docker when running with the maps app installed would start throwing out Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7] FATAL: remaining connection slots are reserved for non-replication superuser connections and Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7] FATAL: sorry, too many clients already. One of the searches I found stated that it could be client connections are not closing on the backend side and as a temp measure to increase max_connections. I increased to 200 then hit the NC server with a maps refresh and it quickly rose from 8-9 connections to 127-129 connections to the DB (watched through the query tool in pgAdmin) but then dropped back down to 8-9 connections not long after. I ask this as I did not find much in my google search with this error related to Nextcloud so I assume I either misconfigured something or, everyone else is just smart enough to increase max_connections to begin with. Also, in the Nextcloud guide you referenced a "go" file for DB tuning. Where would one find this, or if I missed a guide that has this mentioned in more detail can you point me in its direction? Would like to read up on that some more. Attached image with the database errors. I know there are other errors as well (I think they are directly related to the maps app) that I will look into later but I am focused on the DB errors as those one bring Nextcloud to a halt.

Yup, this is all it was, thanks for the help.

CrushFTP Further playing around, I can access crush on my test server using the edge (chrome) browser, I cannot access crush on my main server through edge. The crushFTP.log looks fine until I try and access crush on my main server then it gets those long log entries. Confusing part, I can access crush on my main server and test server using chrome browser just fine.

Not sure what is wrong, but I am sure it is something with my server. I installed the crushftp docker on my test server with the same port assignments and network settings (stock) and seems to work great.

It is in bridge, I only changed a couple port numbers that were already being used by other dockers.

CrushFTP.log Here is the log, only thing I changed is the wan IP. Question, if I change the ports that I want to use in unraid during setup is there a config file somewhere that I also have to edit?

I probably did something to muck this up. Once installed and the container starts I cant access the ui. When looking at the log this is what I get. Is there a permission I am missing? Unzipping CrushFTP... Creating default admin... Admin user written to:./users/MainUsers/ cat: can't open '/etc/system-release': No such file or directory CrushFTP is not currently running... cat: can't open '/etc/system-release': No such file or directory Starting CrushFTP... OK

I clicked on vnc.html and it brought up the VNC page in the browser, then clicked connect and it started the rest of the install process.

Thanks for all the help

Yup, missed that some how, removed and recreated the SMB share but sailed right past the remotes folder instead of the disks folder. I think what got me is that the original folder under disks is still there so I just automatically thought there it is lol.

I seem to be having the same issue as cferra and squid. I can see the full network share if I click on the mount point, but I can only see one folder inside the docker (should be two) and none of the subfolders. I also updated UD to 2020.10.21. unraid-diagnostics-20201211-1710.zip

NVM, found out that remote access check does not work when using custom URLS on the plex forum.

After setting up plex behind the reverse proxy does the Remote Access always show the Red ! and say not avaliable outside your network? Or does it mean I still have a problem to sort out?

Did you ever figure out a solution to this?

I am seeing this as well. Originally I didn't notice because I just dumped a bunch of movies in a test directory to play with and when I checked it was still converting them. It wasn't until after all pending tasks were gone did I see that most of the movies did not convert as there were no failed in the list. If I restart the docker it starts trying to convert again and all that are left either stop immediately or go a few % then stop, but still nothing in the failed list.

My unraid box is running on a 5930k and I just let unmaniac use it all. Avg times so far are around 1hr36min for a 1hr52min bluray rip with only one worker running. A 43min tv show took around 50min with 3 workers running. I am seeing similar results in my tests so far but is going to most likely vary a lot depending on the original file.