binhex

Community Developer
  • Posts

    6732
  • Joined

  • Last visited

  • Days Won

    25

Everything posted by binhex

  1. i need a full log, do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  2. are you also setting the WEBU_PORT?, this needs to match, see this from the readme:-
  3. yeah delugevpn is special, it has to be to prevent ip leakage from occurring, ok take a look and ensure you aren't getting blocked via your firewall (pfsense?) also check any vlan rules arent blocking (if present), ensure its not the host running the web browser thats a problem so try other hosts and different browsers.
  4. that looks like a clean start from the small snippet of the log you have provided, have you changed lan network range?, created more vlan's?, reconfigured firewall etc?.
  5. what is the network for the host running the web browser?, is it also 192.168.2.x?
  6. i cant explain why your ports are switching around but port 8008 is NOT the default port for this container, its set to 8000 out of the box, and altering the container side port should never be done (one exception is qbittorrent), i can only assume you changed the port from 8000 to 8008 at some point due to a port clash with another container. proof link:- https://github.com/binhex/docker-templates/blob/d63dfd036d1694a0f2a20983db10ba18409db4ca/binhex/crafty.xml#L29-L31
  7. here is my stab at explaining this common newbie misconfiguration, Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  8. are you sure of this?, are you putting in the external ip and the port as shown in the supervisord.log?, you cannot enter in your isp's ip address as the port will not be shown as open.
  9. you need to add the wireguard assigned network to the value for env var LAN_NETWORK, using a comma to separate the values, so you should end up with LAN_NETWORK value defining your LAN and your wireguard network.
  10. from your log:- AUTH: Received control message: AUTH_FAILED see Q16:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  11. ok problem 1. (there maybe others), you cannot allocate a static ip for the container that matches your LAN_NETWORK, so either set the container back to the default 'bridge' network and let docker assign an ip to the container, or change the static ip for the container to be in a different network to your main lan and unraid subnet, e.g. create a new docker bridge network and define it as 10.0.30.0/24:- docker network create --subnet=10.0.30.0/24 vpn-bridge then set the vpn container to use the 'vpn-bridge' and set the static ip to say 192.168.30.10, if you want to allow ALL hosts on your internal network to have access to the vpn container then set LAN_NETWORK to be 10.0.20.0/24,10.0.0.0/24 then for access to the vpn container from sonarr you simply point sonarr at the ip address of your unraid server (not the static ip of the container) and port chosen for the qbittorrent container. in short, set the container to use the default bridge, or create new docker bridge network that is not in the lan range and set the container to use that.
  12. what is the difference between: and: there obviously is a difference but without any detail its hard to say, what is 'the same subnet' ?, are you sharing networks with other containers with the rtorrentvpn network?, are you talking about the docker network?, are you talking about a seperate vlan?, as much technical detail as possible is required here, screenshots of it failing would be useful. if a machine running your web browser is NOT in your defined LAN_NETWORK, in your case 10.0.20.0/24 then it will be blocked, this is a security feature of the container and prevents ip leakage, if you have multiple networks then you have to add them into LAN_NETWORK (comma separated). also please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md EDIT - ahh i see your more detailed post here, ok let me read up on your comments:- https://forums.unraid.net/topic/46127-support-binhex-rtorrentvpn/?do=findComment&comment=1042395
  13. i would say this file is corrupt, try renaming it and then restart the container to force regeneration, looking at the file it contains login information and name of server etc, so expect some reconfiguration, alternatively restore this file from your backups from a previous date.
  14. hmm ok i can only assume isues with the endpoint you are attempting connection to, try a different endpoint.
  15. no obvious issues there, so i suspect you have misconfigured the LAN_NETWORK, from your log:- LAN_NETWORK defined as '192.168.1.0/24' see Q4 :- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md edit - if your lan is correct (sounds like it maybe ok from the ip you listed above) then attempt access from another device on your network, also try a different browser to ensure your issue isnt browser related.
  16. i see this specified in your wireguard conf file, from your log:- DNS = 193.138.218.74 perhaps there is an issue with this name server (assuming its mullvad?), try removing that line from your wireguard conf file, this should then force use of the nameservers defined via NAME_SERVERS env var.
  17. Ignore that message it is not critical and is caused by a bug in plex, check your Plex log, probably database corruption would be my first thought as this is quite common Sent from my CLT-L09 using Tapatalk EDIT - just to expand on this now im not on my phone, see Q4 and Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  18. That env var is for user specified options for rclone, unless you know what you are doing then don't use this option, it won't fix your current issue. Sent from my CLT-L09 using Tapatalk
  19. I'm out of suggestions for now, all I can tell you is it does work fine for me and others so the issue is at your end, I just don't know what could be causing it Sent from my CLT-L09 using Tapatalk
  20. It is free for pushes and pulls (limited) I'm assuming what you are referring to is automated builds on docker hub infrastructure, this is no longer free, check out GitHub workflows instead. Sent from my CLT-L09 using Tapatalk
  21. i htink you got something blocking url redirection, try putting this in your browser:- http://<unraid servers ip>:5572/#/dashboard
  22. im assuming when prompted to login (as shown in your first screenshot) you put in the WEBUI_USER amd WEBUI_PASS values right?, can you try a desktop pc not smartphone/tablet, it might be the browser you are running is not compatible
  23. ok that looks alright, the above is the port the web ui uses, so you should be attempting connection on:- http://<unraid ip address>:5572 does that not work?, if not try a different browser, watch out for adblocking extensions too, also check for any firewall running that might be blocking port 5572.
  24. ok can you please share your docker configuration, if you are a unraid user (not sure as your media share name looks odd) then easiest way is to edit the container, change something, change it back to what it was, click apply then copy and paste the entire output here, else if not unraid user then paste your docker run/compose file here.