Beiträge von mrkrabs

    to edit files, you can conect with winSCP and simply edit file, no permission problem if you log as root.

    What would be the point in File Browser then if you can't actually edit or delete anything? Apologies but the permissions of these folders somewhat confuse me. Why must recursive permissions be checked every time a container or the system boots. I expect this may be normal behaviour, but I don't understand why. Thanks!

    I've been using OMV with Docker for over a year now and it has been really solid. I've only had a few minor issues here and there. One of them being applying Recursive permissions to files and subfolders. It seems that if I reboot a Docker container, I have to keep re-applying Recursive Read/Write/Execute to the config folder of the rebooted container.


    Example: I tried to change a port with AdGuard container by editing the .yaml file, but when connect to my /data share (where I store Docker configs) using File Browser to edit the .yaml fole in the agh directory, I get 'Permission Denied'. I then have to go to OMV and apply Recursive Permissions to files and folders in the /data share. I have to do this every time a container is restarted. I'm quite sure this is expected behaviour, but what is the best way to deal with this problem? I would just like the root account to have read/write/execute to everything in this share. For these containers, I usuaully set PGID and PUID to 1000.


    I always get myself confused with permissions but in this situation, it would be nice to set them so I don't have to keep applying recursive permissions. Really appreciate any help. Thank you! :)

    Install the kernel plugin from omv-extras and then you can install the proxmox 6.5 or 6.8 kernel. That should address the quicksync issues.

    This is correct. Thank you! Transcoding now working fine again. I'm a bit confused why it suddenly stopped working as I'm quite sure I was on a 6.1 or older kernel with no issues but regardless. It is now fine again. I'm glad you posted this message because I wasn't sure if the Proxmox kernel would work correctly. All seems fine now. Many thanks!

    Hi folks,


    I'm trying to find the source of this problem. Plex hardware transcoding has suddendly stoppped working and I'm not sure why. It has been working fine for the past 9 months or so. I'm wondering is there an issue with the kernel I am using below. I believe this is the latest available but from what others have said, Quicksync issues have been fixed from kernel 8.2 onwards? Appreciate any suggestions. Thank you.


    6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

    I think this is now sorted. It looks like it was Nginx Proxy Manager that was causing the issue. I deleted this entirely and set it up from scratch again. It's working great now, and if it still works after the next batch of Radarr/Sonarr updates, then that should be it sorted. I have no idea why this was happening but either way, it seems to be good now, fingers crossed!

    This is now working with the latest Business STS Edition 2.20.1


    You can follow the instructions to update here or follow the below instructions. Remember to back up first!!!


    Stop and remove the current Portainer version


    Code
    docker stop portainer


    Code
    docker rm portainer


    Pull the image

    Code
    docker pull portainer/portainer-ee:2.20.1


    And deploy (default ports used here)

    Code
    docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:2.20.1


    I can confirm that this is working again on mine.

    I use NPM and access several containers externally but I don't use Portainer, all containers are configured with the compose plugin. Containers are automatically updated every week by the compose plugin. I have never had access issues after updates on any of the containers.


    Could this problem be related to Portainer only? Have you searched for similar problems on github in Portainer?

    Thanks for the reply. Portainer was my first suspicion too however, I tried both restarting and stopping Portainer completely from the console and even when it was stopped, the issue was still there. I then thought that maybe theres an issue with Nginx, but restarting the Nginx container didn't fix it either. Pinging also doesn't help because all pings seem to complete ok. I've had a look at the logs in Sonarr in this latest issue and there's nothing there of note. It's been a real head scratcher for me to troubleshoot! Thanks.

    Hi folks.


    I've been experiencing an issue that I have so far been unable to troubleshoot. I have about 10 Docker containers that I access externally using Nginx Proxy Manager. Namelt Sonarr, Radarr, Plex etc. Each of these containers are all accessible internally, but often after updating a container, the external access would stop responding and I would eventually get a 502 Bad Gateway error. This has happened to multiple containers and I have not been able to identidy a pattern.


    Example: I update Sonarr via Portainer. The container reboots and the update is successful. Accesing Sonarr via interal IP address is perfect however, accessing externally via Nginx suddently times out. All other containers I have set up via Nginx are working fine. I've tried restarting Portainer and even stopping it completely, but this makes no difference, so I'm fairly sure that has nothing to do with it. I've also tried restarting Nginx containter and recreating Nginx host entry. The only thing that's ever worked is rebooting OMV. When I do this, sometimes another container will start doing the same thing. So Radarr might then become inaccessible externally, but Sonarr starts working again.


    I should emphasise that this does not happen every time I update a container. Only sometimes, and it seems to be a different containter for reasons that are so far unknown to me.


    I'm asking here first because the only solution I've found so far is to reboot OMV completley, then either they all start working again, or another cointainer becomes unresponsive externally. I am not sure where to troubleshoot this. Really appreciate any suggestions. By the way I'm currently using the latest OMV 7.0.5-1 build. Thank you!