Jump to content

Xerazal

Members
  • Posts

    6
  • Joined

Posts posted by Xerazal

  1. 16 hours ago, itimpi said:

    A gigabit LAN silently downgrading to 100Mbps normally means that there is at least one twisted pair not making connection in the cable between the router and the server.   This can be either a broken wire within the cable or a pin not making contact at either end.  I would suggest trying different cables and/or ports.

    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.

  2. 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,

    Screenshot 2024-04-15 015415.png

     

    a portion of ifconfig,

    Screenshot 2024-04-15 015618.png

     

    and diagnostics file.

    yggdrasil-diagnostics-20240415-0151.zip

  3. 6 hours ago, Kilrah said:

    2 options:

    1) Change the user in the advanced settings of the cronjob container to 99:

     

    image.png.64f9bad9c2437eaccbb50f34f83bd7e4.png

     

    2) remove the --user 99:100 in Extra Parameters of the knex666 template, then on unraid terminal 

    chown -R 33:33 /mnt/user/appdata/nextcloud/ (or your folder)

     

    It should then work fine. 

     

    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

  4. 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 nextcloud  

     

    Unable 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

    image.png.49f92c7e6f1b38d3c2b77e59fe6eba08.png

     

    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)

    image.png.4b6254ab78eac6868da9b0b58d31027f.png

     

    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.

×
×
  • Create New...