Jump to content

wgstarks

Members
  • Posts

    5,366
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by wgstarks

  1. Netherlands no longer supports port forwarding (PIA change). You’ll need to switch endpoints. See 2nd post in this thread.
  2. Did you select which packages you wanted to install in Settings>Nerd Pack?
  3. Working for me. Edit: Maybe this link will work for you- ***removed*** Please let me know if you get it so I can take it back down.
  4. The gfjardim beta script does not require patching. If you want to use either of the others they probably will.
  5. Perhaps Binhex can confirm, but I believe that’s normal. I know I see it constantly in my log as well as the ones posted by others.
  6. If you access Deluge with a thin client the column is still there.
  7. @snarrett You need to switch endpoints- https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=648412
  8. Does PIA have a list somewhere showing bandwidth or did you just get this from your own testing?
  9. It’s been up and running for months. Just switched the nl ovpn for Germany. Also Toronto but that didn’t work either.
  10. I switched to Germany. The docker shows that its running but I can’t open the UI or thin client. supervisord.log
  11. Looks like I’m SOL too. I’m guessing I need to find a new ovpn file? Does anyone have a link?
  12. Servers seem to be back up now. Should work.
  13. Worked great for me in legacy using Safari. Took about 40 seconds.
  14. I’m getting <appdata>/DiskSpeed/Instances/local/<diskID>/driveinfo/config.json but looks like no edits are written to this file.
  15. Rescanning Controllers seems to be the cause of the problem. It looks like edits to the drives are saved in storage.json and whenever I rescan controllers storage.json gets overwritten (actually it’s renamed to oldstorage.json) so any edits that were made to it are lost. This is just what I’m seeing on my system. Maybe this isn’t proper behavior?
  16. Same issue with display customizations not being saved across docker updates. Pretty minor issue though.
  17. After updating to beta 2a I see that changes that I made to the drive capacity display aren’t being saved. Would it be possible to save these changes across docker updates? Also, the Mushkin is now detected correctly. Thanks.
  18. Will the docker still auto-update if I installed it manually? CA server still appears to be tits up. Not sure if that also effects updates.
  19. Also, i see that my Mushkin MKNSSDRE240GB-LT SSD seems have been improperly identified as a Toshiba drive. I added the image manually from your database.
  20. VERY NICE I notice I've got several missing models/images though. I see that you show that "they are reported for my review". Does that mean you don't need any more info from me regarding them?
  21. IIRC it writes random bits rather than just zeros.
  22. Each docker has an image which is stored in a docker.img file at whatever location you have set in docker settings. https://lime-technology.com/forums/topic/57181-real-docker-faq/ When you click a docker logo on the docker tab one of the options presented is “Remove”. Selecting this will delete the docker and open a prompt “Do you also want to delete the img”. Selecting yes will delete the img.
  23. As long as the docker path mapping’s are the same you’ll still have the torrents.
×
×
  • Create New...