Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

strike

Members
  • Joined

  • Last visited

Everything posted by strike

  1. @krobson17, @wgstarks Regarding the low speed, one thing you can try is to switch to a tcp connection, preferably TCP 443 or 53 if possible. Where I live many ISP's throttle UDP VPN connections, dont ask me why. When I was a PIA member I had to switch to a TCP connection to get the speed I wanted. So try to download a new opvn file which connects over TCP. I don't know if this is possible with PIA now, but it was at least when I was a member. If you can't find a new file ask PIA if they can send one to you if they support it. If not I would switch provider, AirVPN maybe. If you guys have checked your settings and everything is ok then I'm almost certain you're suffering form ISP throttling.
  2. I have tried vyprvpn (many years ago), PIA, Expressvpn and AirVPN. AirVPN is by far the best one of these, IMO anyway. AirVPN lets you mask that you’re using a vpn by connecting over SSH/SSL or even TOR. They also do some kind of sweet routing trick that lets you access certain websites like BBC iplayer form any of their endpoints, not just UK ones. Regarding vyprvpn it might not work with delugevpn:
  3. No vpn providers has magic servers.. To do p2p you MUST have an open incoming port to get decent speed. That is just the way it’s designed. If you guys are using PIA, the only thing you must configure is VPN_PROV = PIA and STRICT_PORT FORWARD = yes. And you must be connected to one of the endpoints that support port forwarding. If you have done that, then this container will take care of the port forwarding for you automagically.
  4. Been a long time since I've configured this (6.1 days), but if you guys read the info on github and the readme located in the plugin folder I'm sure you'll be able to figure it out. I'm using key based login only and it works like a charm. Github: https://github.com/docgyver/unraid-v6-plugins Readme located on your flashdrive in /boot/config/plugins/ssh
  5. Hmm..Then I'm not really sure what the issue is. I can't see anything obvious in the log, better wait for someone else to chime in.
  6. You're supposed to have only one .ovpn file in the openvpn folder, remove the rest. The vpn tunnel is up so if you're not getting to the webui it's maybe because of the extra files you have in the openvpn folder or your LAN_NETWORK is wrong. What is your unraid IP?
  7. Just ignore that warning. Are you able to get to the webui now after making those changes? If not please enable debug logging by changing the DEBUG variable to true. Delete the /config/supervisord.log, start the container and let it run for a few min and post the entire log here. Remove username/pw of course. As for the incoming port you need to check if your provider supports it and do whatever you have to do to open a port. Then add that port in the deluge webui settings not the docker settings. Do not open any ports on your router.
  8. Couple things here. First change VPN_PROV to custom, second remove what you have in VPN_OPTIONS and leave it blank. I haven't tried vyprvpn for a long time so I don't remember if they support port forwarding. But if they don't you might want to change provider as you won't really be able to torrent as torrenting require an open incoming port. If they do support port forwarding you need to use whatever endpoints that support it, I doubt the one you have chosen does.
  9. np One thing I missed when reading the log last time: As stated in the log, if you have special characters in your password this can cause authentication issues.
  10. You have a successful start and are connected to the vpn. One thing tho, you should have only one ovpn file in the openvpn folder. And you must pick one of the endpoints which support port forwarding or else you won't be able to get any decent speed as torrenting require an open incoming port. The Netherlands is a good one, remove all the rest of the opvn files you have in the openvpn folder. If you want to change endpoints later just replace the opvn file with another endpoint and restart the container.
  11. Please enable debug by stopping the container, setting the DEBUG variable to true, delete /config/supervisord.log. start the container and let it run for a few min then post the entire logfile here. Be sure to remove any username/password before you post it.
  12. Remove whatever you have in the VPN_OPTIONS variable. This is for advanced vpn options only, so if you don't know how to use it leave it blank
  13. Please read the FAQ, specifically Q8
  14. You can. Don't know about that error tho.. Maybe you have 2 containers with the same name?
  15. You have defined your PIA username but not your password. Think you should be good to go if you define your pw as well..
  16. Whatever floats your boat
  17. Probably a configuration issue in the extension. Have you tried including http:// in the address? some apps require it and some don’t. I've never tested that extension so I wouldn’t know. What OS are you running chrome on?
  18. I remember having that issue once, don't remember what I did to fix it tho. Think it got fixed when I nuked the docker image and pulled the containers again. I could be wrong, but if all else fails you can try that. Doesn't take long, you'll be up in about 10 min with all your dockers back up if you use the "previous apps" section in CA. Also before you try that, stop/restart the docker and if the labels plugin is unchecked again don't check it. Just try to send a test torrent to deluge with sonarr/sickrage/radarr or whatever you're using and check if the label gets added to the torrent anyway. I kinda remember trying that too, but I don't remember if that was the thing that fixed it.
  19. Take a look at the link in the post right above yours and you'll have the answer..
  20. lol, glad I could help
  21. Aaah, I see it now. You have put the endpoint address in the VPN_OPTIONS variable.. This is for advanced OpenVPN options only. Remove that and I think you should be good to go
  22. Then I don't know, better wait for the expert. But one thing you can do is to edit the container and set the debug variable to true, before you start the container again delete the supervisord.log in config, start the container and let it run a few min, then post the log here. Edit: Be sure to remove your username/password
  23. Well, something is obviously wrong with the username an/or password. What happens if you delete that extra line? Are your sure the username/password is correct? Do you have any special characters in the username/password?
  24. First of all you shouldn't be forwarding incoming ports on your router. When you're on a VPN connection the port forwarding must be done on the VPN provider side, not yours. Second, this container does all the "port forwarding" for you if you're using PIA. The only thing you have to do is choose on of the end points that allows port forwarding. The Netherlands would be a good choice I think. I've tried a few VPN providers but the one thing that has been common for all of them is that you get the best speed from the Netherlands, don't ask me why. Third, you could be suffering from "ISP throttling". Where I live some ISP are throttling VPN UDP connectiions, again don't ask me why. If that is the case it can help if you connect over a TCP port instead. Been a while since I've used PIA, but I believe you can choose to connect over TCP, at least you could when I was a member.
  25. Edit the docker and set the DEBUG variable to true. Also delete the log before you start the container again, let it run for a few min and post the new log here. This was also in you log: [warn] Username contains characters which could cause authentication issues, please consider changing this if possible [warn] Password contains characters which could cause authentication issues, please consider changing this if possible

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.