Jump to content

binhex

Community Developer
  • Content Count

    4437
  • Joined

  • Last visited

  • Days Won

    10

binhex last won the day on August 23

binhex had the most liked content!

Community Reputation

374 Very Good

About binhex

  • Rank
    unPaid

Converted

  • Gender
    Undisclosed
  • URL
    https://goo.gl/psyfQx
  • Personal Text
    Addicted to the internet

Recent Profile Visitors

6667 profile views
  1. Lol my question made it in, I'm sure I can beat 4560 @SpaceInvaderOne I've just got to dust off my copy of m.a.m e and get some pizza in to help me focus 😁😁
  2. ok the good news is, i see no sign of corruption mentioned in that log, the bad news is i got no idea why you are having an issue. have you tried another browser?, it could be some caching issue, or even tried accessing it via smart phone or something like that?
  3. i thought so, in that case you are running into the unraid bug with sqlite databases, you can simply restore all your files located in /config (assuming you have a backup) but this will only fix it temporarily until it happens again. for a longer term fix your options are:- 1. roll back to unraid 6.6.7 or 2. buy a cache drive and move application config/database/metadata from array to cache or 3. wait and hope limetech fix the issue in 6.8.0 (still in release candidate stage). obviously whatever option you choose you will still need to either restore your database back to a working version, or if no backups then you would need to delete everything in /config for this container and re-configure from scratch..
  4. a quick bit of googling lands me here:- https://forum.teamspeak.com/threads/121642-loading-VirtualServer(1)-failed-to-start-error-invalid-group-ID with this:- so im going to guess you are using unraid 6.7.2, and you have /config for this container stored on the array (not cache drive), am i correct?.
  5. lets rule out database corruption firstly, can you attach the file '/config/Plex Media Server/Logs/Plex Media Server.log'
  6. if you change the value of PUID and PGID then you MUST delete the file /config/perms.txt and restart the container.
  7. yes, if you change the values of PUID and PGID then you MUST delete the file /config/perms.txt and restart the container, otherwise the permissions will not be reset for the newly defined PUID and PGID values and permissions will be wrong causing all sorts of issues.
  8. See post #2 in this thread Sent from my CLT-L09 using Tapatalk
  9. The only thing I spotted is that you have 3 plugins enabled, and they may not be compatible with deluge v2. What you could try is rename core.conf to something like core.conf.old and then restart the container see if you can access the web UI Sent from my CLT-L09 using Tapatalk
  10. Yes that is a fourth option, although quite a bit of effort when compared to a simple downgrade to unraid 6.6.7 [emoji16] Sent from my CLT-L09 using Tapatalk
  11. cache drive is the norm, i fear you may well have the same issue again :-(, if you want to prevent this then your options are:- 1. roll back to unraid 6.6.7 or 2. buy a cache drive and move plex metadata from array to cache or 3. wait and hope limetech fix the issue in 6.8.0 (still in release candidate stage). just to be clear this is not a plex issue or a issue regards this image, its a SHFS/FUSE problem with unraid and sqlite databases (affects more than just plex).
  12. im running sonarr and do not see the above, im assuming you have tried a restart of the container with no obvious improvement?
  13. ok, i would of liked to of checked that log but hey you are up and running, are you running unraid 6.7.2 and do you have plex metadata located on your array?, if so you are likely to of had the database corruption issue, which most likely will bite you again.
  14. hmm odd!, to try and remove the human factor here try using the copy and paste function of novnc, its on the left hand side as a pop out style set of buttons, paste it into the paste pop out and then you should be able to right click in the novnc window and paste it in there.
  15. thanks for the post, always nice to have people post just cos they appreciate your work, cheers for the beer.