wgstarks

Members
  • Posts

    5125
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by wgstarks

  1. This should be reported to the Sonarr dev team.
  2. Looks like some corruption in the db. Maybe caused by the invalid V3 tag. If you have a recent backup of the database prior to using V3 you might be able to restore from that. Otherwise I would suggest posting in the Sonarr forums for help recovering the db.
  3. Any error in the browser and docker logs?
  4. Well it's no surprise I couldn't find it then. Nobody ever looks there.😁😁😁
  5. @trurl Thanks. I thought I had seen something like that but couldn’t find it when I needed it and don’t like to trust my memory much the closer I get to retirement.😁
  6. I know that a clear for unraid writes all zeros to a drive. I have heard that it's possible to recover data from a drive that has been cleared in this manner because the overwrite was done in a known pattern (all zeros). I'm not sure if this is true or not but just in case it is, is it possible to use this plugin to overwrite a drive with random zeros and ones?
  7. Was replacing an old HDD yesterday and tried using the locate button in this plugin to verify which slot the disk was installed in but never could get it to do anything obvious. I’m assuming that the button would be providing a signal via the disk activity light but never saw anything that stood out. Of course most of the lights were blinking with random activity. Exactly what should I be looking for?
  8. Perhaps @binhex has some idea regarding the log entry. The fact that it's [info] makes me think it's not a concern though.
  9. Here’s a link to a YouTube video regarding routing a docker through another’s vpn. https://youtu.be/znSu_FuKFW0?si=_jqO_o0R8ztegPmM Sorry, don’t know anything about HexChat. I would suggest posting in their support thread.
  10. Just to be sure you understand, this is a proxy server that will allow other dockers to use the vpn connection (Sonarr, Radarr, etc).
  11. That file should have been populated when you enabled privoxy with default settings. Most are commented but I know the listen port is enabled.
  12. appdata/binhex-qbittorrentvpn/privoxy/config
  13. The only thing I see out of the ordinary is that you have defined VPN ports. That’s not normally necessary.
  14. Are you sure it’s not a path mapping problem? It’s possible you could be creating directories in ram and writing files to them. You can post your docker run command if you’re not sure. Be sure to redact users/passwords.
  15. You can roll back to any version using the dockerhub tag numbers in the repository field of the docker configuration. The format is <repository name>:<tag number>. The repository name should already be entered so just type a colon and then a tag number and hit apply. Looks like the last 4.5 tag was 4.5.5-1-04.
  16. The OpenVPN credentials are the right ones to use but your logs would show “auth failed” if it was your credentials.
  17. That warning is standard. The only requirement for port forwarding with this docker is to use a server that supports port forwarding. If you provide some details someone may be able to help.
  18. I’m not seeing anything obvious. I wonder if it could be a server issue???
  19. Attach your supervisord log to your next post as well as your docker run file. Be sure to redact users and passwords.
  20. Pinned at the top of the page 2nd one down.
  21. How are you entering the password? If you're using copy/paste maybe try typing it into the password field. Also, are you sure you're using the correct credentials? I know PIA has separate credentials for VPN login and website login.
  22. You could test this by disabling 2FA. There could also be other reasons- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Scroll down to Q16.