![](http://content.invisioncic.com/u329766/set_resources_34/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
EC28
-
Posts
91 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by EC28
-
-
Thanks!
So it would need to be --user nobody:users
-
How would I format the user flag in the field? Currently I have the routing through the bittorrent container for VPN use.
-
Looks like he's getting ready to solve the issue further. Once we can set the files to 777 we should be good, right?
-
-
On 3/27/2024 at 10:10 AM, nmkaufman said:
I will play around with it, this weekend.
I believe the problem is that it's creating files, owned by ROOT, while other containers use NOBODY, by default.
It's not setting permissions that allow other users to access the files.
The easiest solution would be to set the UMASK, but I tried passing a UMASK environmental variable to the container, and it didn't seem to work. I did see a reddit thread where someone claimed this worked, though, so I'm going to further experiment.
Did you ever figured this out? Having the same issue when it comes to Lidarr.
-
On 11/15/2023 at 8:49 PM, martinkeat said:
Can you use google icons for this? Because if you could that would be awesome. https://fonts.google.com/iconshttps://fonts.google.com/icons
I just tried it using the base64 converter on the link in the folder creation page and it worked!
-
3 hours ago, Kilrah said:
Got it. I can live with it there. I'm really just using Nextcloud to be able to share external storage with other people, so it's fine.
One other thing though, my nginx proxy manager doesn't seem to be working with it. Is there something special I need to do in NPM or the config to be able to access it externally? Thanks for the help, this container is blazing fast.
-
So I have gotten it to this point by doing some heavy reading and trial and error. Here is my template page. I'm trying to keep things on the cache and keep things neat where I can change things and tinker when I want. The cloud is actually up and running. Had to use the commands from earlier in the thread to change ownership and permissions, but that let me install it into the appdata directory that I picked. Or so I think anyway. The problem is, I don't see any of the config files when I look for them. The other screenshot shows all the files I see in the appdata folder. So I have no idea where the actual config files are going. In spite of that, you can see my cloud is up and running somehow. This thing has one hell of a learning curve.
-
I'm slowly making progress. Messing with ownership and permissions and have gotten a little bit further in the process.
-
Spoke too soon, now I'm getting errors with the LSIO one as well. I did change the cache to exclusive though, so that may be a part of it as well. They both like to try to mount on /mnt/cache/ and not /mnt/user/appdata/, so who knows what that throws off. I'm just gonna have to wait on the man for some more help I think. Let me know if you get it up and running.
-
1 hour ago, ceverson said:
Hello so i installed the container for nextcloud and CRON jobs but i can't create folders. I am using NGINX Proxy Manager. However what seems to be occuring is in the Nextcloud docker container it is using Apache and Apache restarts when I restart the container. I tried disabling Apache in the container itself but that shut the container down. How do I make Nextcloud fully use NGinx. The reason I say fully is I worked through all the other NGinx based errors last night and they took affect so I believe my issue is strictly Apache is enabled and getting in the way
I'm wondering if the issue I'm having isn't somewhat related to yours. I tried to re-install the LSIO docker of nextcloud and it worked fine again just now. There's something different in the ffmpeg and official versions that seems to throw my system off. It's like it can't see it's own data for some reason.
-
1
-
-
I guess I could have seen that answer coming, haha. Working with fresh installs. Here's the log.
-
Hey there, racking my brain trying to figure out what I'm doing wrong with this docker. I had it running fine with the lsio docker, but wanted to switch to this one for the ffmpeg support. I've installed mariadb as normal and when I choose the db to connect to on install, I'm getting this error when I try to open nextcloud:
Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.
Any ideas what I'm doing wrong?
-
Kind of what I was figuring, thanks.
-
So....it happened again. Guessing I might have an issue with that drive? I was able to recover it the same as before, but this is popping up now. And I'm not seeing that plugin in the nerdtools pack.
-
That fixed it, thanks!
-
1
-
-
One thing I've noticed is that when I run the script to check for errors, it's still showing all the errors from earlier. Any thoughts on that?
-
I think that fixed me up sir. Thank you so much for your help.
I created the user script to run the scrub every week and check for errors. Anything else I need to do?
-
-
Gotcha. Looks like about a 6 hour run. We'll see. Thanks for all your help so far.
-
Do I check repair corrupted blocks?
-
-
Yeah, docker won't start for some reason. My VM is working fine.
-
Ok, somehow it found it now. Docker didn't start though. Going to try to start it manually and maybe reboot again.
[Support] manuel-rw Docker Support thread
in Docker Containers
Posted
Getting this error when I add the user flag. If I take the tag back out, it functions fine.