strike

Members
  • Posts

    609
  • Joined

  • Last visited

Everything posted by strike

  1. OH, then you don't want to reverse proxy it with swag.. That's what's swag is for, making it open to the internet ,securely. But maybe you can copy the certs from swag to nextcloud, idk. You'll have to google it as I have no clue, but I THINK it can be done.
  2. Just set up a subdomain. @SpaceInvaderOne has a video on how to set up nextcloud with swag: https://www.youtube.com/watch?v=I0lhZc25Sro
  3. What is your network type? And what IP does your unraid box have?
  4. See Q25 and maybe 27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  5. No point in posting the log if everything is working. Maybe the vpn server you connected to had issues. You won't be able to see the webui before the vpn tunnel is up.
  6. If I have to guess it's probably your LAN_NETWORK being wrong. See Q4: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md If you still can't get it to work do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  7. When you read the faq to get the webui working it didn't occur to you to continue reading it? See Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  8. That can be an option as well, but you better take that up with them as you said. Speed will vary across vpn servers as some have higher load than others, and this will constantly change. So to pick a server that is better than the other is just pure hit and miss and can change fast. But European servers tend to be faster when using p2p. That's my experience anyway. How will you know tho? When you switch vpn servers your connection will reset, and you might not even get connected to the same peers as before. In your settings you probably have only about 150 total connections or something set up. As in the example in my last post. Say you have a torrent with 500 seeders, and you're connected to 100 seeds and 50 leechers on this torrent. That's a total of 150 connections. Only 2 have an open incoming port of those, so you get 8MiB/s, which is the max those peers can upload. You switch vpn server and connect again to 100 seeds and 50 leechers. And none of them are one of the peers you connected to before, and of those there are now 3 with an open incoming port so you get 10MiB/s. Say you switch vpn servers back and forth, you will connect to different peers every time, so the speed will also vary not only based on the load on the vpn server but the speed of those you are connected to as well which can change every time. So again, how can you know that, when you are not even connecting to the same peers as before? IMHO available connections (an open incoming port) is the number one factor when it comes to speed in p2p. In any case, when your subscription is up you'd be better of with a provider that supports port forwarding. In fact, not just you will be better off, but all the other peers that you will encounter will thank you too
  9. it did read the entire thing. And why not? Why shouldn't that explain it? If noting else changed in your settings or network it's either that or slow vpn server. If you don't have an open incoming port your speed will always fluctuate. Today you get 8MiB/s tomorrow you might get 2, 10 or 20. But as I said you almost certainly do not get full speed. This guy from reddit says it well: Source: https://www.reddit.com/r/torrents/comments/agwhiq/why_opening_bittorrent_ports/
  10. Regarding the speed. I'm sure you're already aware of this, but NordVPN does not offer port forwarding. And as long as you keep using them you will never be able to fully utilize your connection, as that requires an open incoming port for other peers to connect to. So your speed will always fluctuate but you almost certainly will never be able to get full speed. So my advice is, stop trying to get better speed or switch vpn provider to one that offers port forwarding.
  11. Your template is too old and you need to add it yourself. On the bottom of the page click "Add another path,port..." And set it to variable, as the key you set "VPN_INPUT_PORTS", and as value you put the port. If you have multiple ports separate them with comma. Edit: Also see Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  12. Been years since I was using PIA, but maybe I can answer you anyway. Always use the most recent version of any software unless it for some reason gives you issues. PIA have .ovpn files for both TCP and UDP (at least they used to when I was using them). Use UDP if you can, as that is the fastest protocol.
  13. See Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  14. First of all, you need to change your password asap, as it's in the log you posted. Second, set the STRICT_PORT_FORWADING to no, this setting only applies to PIA users. You need to have an open incoming port to get good speed. Have you port forwarded a port? It's unclear to me if purevpn offers port forwarding or not. In a quick google search, their website talks about port forwarding and what it is, but I can't see anything about if they offer port forwarding or not. I saw something about you need to download their app maybe? Are you on a private tracker? If so most of them require an open incoming port. And if you don't have it they won't let you download or it will be very slow. Try to download a well-seeded torrent on a public tracker, like a ubuntu ISO or something. Then you should at least be able to download, but the speed will be much slower than with an open incoming port. If you can download it on a public tracker you know it's definitely a port forwarding issue that's causing you to not be able to download on your private tracker. And there's no point in testing the speed on speedtest.net, that only works for web browsing and web downloads. The speed you get on torrents has nothing to do with your web browsing/web download speed as many factors are taken into account with torrenting. The only thing speedtest.net will tell you is that you MAYBE can get that speed, if all the conditions are right.
  15. You didn't mention that in your OP, then you must add that subnet to your LAN_NETWORK as well. The point of the LAN_NETWORK variable is to define your network, and all the subnets you listed are different networks. So if you need access from all of them they need to be listed. There is no magical "catch all type networks" you can add instead, AFAIK anyway.
  16. This is wrong. You need to set your LAN_NETWORK to 192.168.10.0,192.168.130.0 You can have multiple subnets defined, just separate them with comma. This container doesn't officially support a customs bridge network, like br0. It can work in some cases but sometimes it does not. If you want to go this route you'd better ditch the web ui and download the thin client and use that. Then you might get it to work on br0. By default all container on a custom bridge network are blocked from the host. This is a security feature. This means they can NOT access other containers on host and normal bridge network. They must be on the same custom bridge in order to communicate. I haven't tried it, but I think you can bypass this by setting "Host access to custom networks:" to enabled in settings->Docker.
  17. This sounds like a volume mapping issue or a wrong path in the downloads section in deluge. Post your docker run command and a screenshot of the downloads section in deluge.
  18. Hardware transcoding doesn't work in this container, reported by many people. Switch to the official one or the linuxserver one and you should be good.
  19. I'm not sure I remember correctly, but I think I saw something in the 6.9 release notes that it's not allowed with no root password anymore. Which is a good thing.
  20. Have you added your subnet under LAN_Network? Remember you're on a different network when connecting remotely over wireguard.
  21. You can add or remove a subdomain to trigger the renewal process. If it fails again be sure to set the staging variable to "true", this will increase the rate limiting so you don't hit the limit when testing. Set it back to false when you have it working.
  22. Make sure to read everything in Q6, there are a couple deluge specific things there you can try if you have tried everything else in there.
  23. When torrenting to get great speed you need to have a port forwarded. NordVPN does not offer port forwarding, so you're out of luck there. Also see Q6: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  24. This is normal and harmless. If you're using PIA there is a script in place to bind the port every 15 min, this is a requirement from PIA side. If you don't bind the port every 15 min you will lose it and it will be assigned to someone else.