-
Posts
6 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Xerazal
-
-
Just noticed this started happening a bit ago. I've had this happen before, but simply rebooting the server fixed it. Haven't had this issue happen in over a year now. But now, doesn't look like rebooting the server is helping.
This is the onboard nic on an asus prime b560-m (here's the link to the specs)
will attach ethtool eth0,
a portion of ifconfig,
and diagnostics file.
-
Is there any way to edit the message of the webhook? I want it to add an @everyone tag at the beginning of the announcement.
-
-
6 hours ago, Kilrah said:
Did option 1. Had to change the perms for the data folder & contents to 99 since, for whatever reason, it was set to 33. Works now.
Thanks
-
On 12/24/2022 at 6:45 PM, Alpha.Ars said:
I'm realy struggeling with the permissions for the Nextcloud cron.
Can't run with the nextcloud basic config. When I run this command "docker exec -u root nextcloud chown -R 33:users * "
the cron works... but then I'm unable to access nextcloudUnable to write to the "config" directory! This problem is usually solved by giving the web server write access to the configuration directory. Or, if you prefer to keep the config.php file read-only, set the "config_is_read_only" option to true. See https://docs.nextcloud.com/server/25/go.php?to=admin-config
when I run: "docker exec -u root nextcloud chown -R 99:users * "
I do have access on nextcloud but the script can't access (just like in the begining)
I was able to fix it once in the past but then I had no access to the nextcloud appstore.
Do you have any hint ?
Having this same exact issue. Using knex666's docker image of nextcloud.
Setting permissions to 33:users lets the cron docker image run the script, but then the nextcloud container can't access anything. Switching permissions back to 99 gives nextcloud access, but then the cron docker image doesn't work.
Unraid keeps switching interface to 100 mbps
in General Support
Posted
Swapped the cable out for another one and that seems to have fixed it. Did it this morning, and so far hasn't stepped down the link speed in 10 hours.
Gonna have to make a few spares for later replacement.