wgstarks

Members
  • Posts

    5125
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by wgstarks

  1. Sorry, I don’t use wireguard. With OpenVPN you can just edit the ovpn file.
  2. The log you posted is just the tail of a log but it shows a successful start of the container. I think I would try switching to another port forwarding server and see if performance improves.
  3. I would think it does. You could test that by switching to bridge. Im sure there’s some way to get this to work with custom networks but I don’t have much experience with them. Perhaps @binhex can help.
  4. Is that the network assignment being used by docker0 in your routing table? Also, did you change the IP in Radarr/Sonarr to match?
  5. Another option would be to whitelist connections from your local network. 172.17.0.0/24 is the network assigned to docker0 in my unRAID machine. You can verify yours by checking Settings>Network Settings>Routing Tables.
  6. I was mistaken. I’m afraid I’m out of ideas. The most common reason for not being able to connect to the webUI is when trying to access it from outside your local network but if you are using a 192.168.50.0/24 address then that doesn’t apply. Are you running any content/site blockers? You may need to whitelist it.
  7. I don’t know that this will solve your issue (might though) but you don’t need to use rw slave for locations on the array. Just use rw.
  8. Post your docker logs. Docker tab>click the icon and select “log”. Maybe there’s a clue there.
  9. Looks like a network DNS issue- Try setting DNS to just 8.8.8.8.
  10. The logs show a successful start. Your docker run command shows that you are still running the current version of qbit though. I would suggest either running an older version of the docker or apply the workaround pinned at the top of the page (2nd post). Also, you don’t want to forget to change your endpoint to one that supports port forwarding once you get the connection issues fixed.
  11. And you are trying to connect from the same local network you have set in the container? Can you connect if you select webUI in the docker tab in unRAID?
  12. I’m not sure if this is your only issue but you changed your webUI port without mapping the new port to the container. https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md See Q4.
  13. Just to be sure, you are trying to access the webUI from your local network right?
  14. You needed to change the endpoint rather than the container setting but regardless, you must have some other issue. Post a redacted docker run command so we can see your configuration as well as a fresh supervisord log (after a restart).
  15. No In unRAID you would just click the docker icon and select “stop”. On the command line enter docker stop <name of docker>
  16. If it is truly missing you can add it back.
  17. It’s going to be /data in the container path and the host path will be something like /mnt/user/path/to/downloads.
  18. Can you also post your docker run command? Again, please redact user/password.
  19. Post your logs. Be sure users and passwords are redacted.
  20. I would suggest attaching supervisord log to your next post. Be sure users and passwords are redacted.
  21. From your log- You have strict port forwarding enabled but your endpoint doesn’t support that. You’ll need to pick one that does.
  22. What version of the app do you have installed and if it’s latest, have you configured a secure password?
  23. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md See Q11. Please be aware that some PIA servers are much slower than others.
  24. Sorry, I may have posted the wrong link earlier. Here is the one I meant to post. https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1329646