Jump to content

j0nnymoe

Members
  • Content Count

    316
  • Joined

  • Last visited

Community Reputation

48 Good

2 Followers

About j0nnymoe

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Seems like you answered your own question 🙂
  2. Fixed image has now been pushed to the repo. It had broken due to the booksonic dev renaming the repo. Looks like they're rebasing booksonic on airsonic currently so we will switch to that once it is released.
  3. Looks like there are some changes upstream so we will need to make some adjustments on our container. For now, please rollback to a previous tag.
  4. Nextcloud isn't designed in a way to deal with the data being accessed another way, hence why they have the external storages app. In theory you should only access the data you have in the `/data` mount via the nextcloud interface otherwise if you're changing files, you have to force nextcloud to reindex everytime you make a change.
  5. No because nextcloud designed it in way that won't work with containers.
  6. I don't actually believe AMD provide the same solutions for using their cards within docker like nvidia do.
  7. It's likely nvidia-smi doesn't support the 710.
  8. I suspect your older cards won't support NVENC or NVDEC either so even if you could get it to run on unraid, you wouldn't get transcoding via emby/plex/etc
  9. It could also be the bonding that is causing an issue here. We've never been able to replicate these issues which is why these are the only way's we know to fix it. But it seems like we haven't been able to replicate these issues because no one within the team that uses the nvidia plugin has any 10gbit networking kit or uses bonding (to my knowledge).
  10. This has been mentioned before in this thread many times. The only things we can find that causes this are: pihole (or some network ad blocker) / MTU changed on unraid host (10gbit cards for example) or some other network configuration. We've never been able to replicate these errors within the team.
  11. Has any of your network changed? Do you have 10gbit adapters installed? Do you run pihole? Like @CHBMB mentioned, we are unable to replicate issues with the plugin like this and we all have different network configurations but from previous discussions in this thread it always seems to relate to: MTU or pihole. There is a script a few pages back that will let you download this manually which you can run via ssh.
  12. Have you changed "anything" on your server and/or your network?
  13. It would help if you provided screenshots of your template or provided the docker run command.
  14. Have you had to change any MTU settings or anything? there's not really much else I can suggest looking at. All previous cases of this is there had been some change to a users network.
  15. Have you changed anything else on your network?