Everything posted by kenv
-
[Support] binhex - qBittorrentVPN
any idea what i messed up with this compose? qbittorrentvpn: image: binhex/arch-qbittorrentvpn:latest container_name: qbittorrentvpn cap_add: - NET_ADMIN devices: - /dev/net/tun volumes: - ${USERDIR}/docker/qbittorrentvpn/config:/config - ${USERDIR}/Downloads1:/downloads - ${USERDIR}/Downloads1/completed:/downloads/completed - ${USERDIR}/docker/shared:/shared ports: - "6881:6881" - "6881:6881/udp" - "8090:8090" - "8120:8118" restart: always environment: - VPN_ENABLED=yes - [email protected] - VPN_PASS=xxxxxx - VPN_PROV=slickvpn - ENABLE_PRIVOXY=yes - LAN_NETWORK=192.168.1.1/24 - NAME_SERVERS=1.1.1.1,1.0.0.1 - UMASK_SET=002 - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - WEBUI_PORT=8090 networks: - traefik_proxy labels: - "traefik.enable=true" - "traefik.backend=qbittorrentvpn" - "traefik.frontend.rule=Host:qbt.${DOMAINNAME}" - "traefik.port=8118" getting TLS handshake failed after starting OpenVPN so thinking it doesnt like my port mapping/config but I'm running deluge in traefik proxy as well so I cant have 8118 and 8080 in use in qbittorrent.
-
[Support] binhex - DelugeVPN
so i deleted everything and rebuilt and now seeing this error haha 2019-02-22 17:56:26,624 DEBG 'start-script' stdout output: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: auth-user-pass (2.4.6) Use --help for more information. presumably its referring to this line in the .ovpn file: # prompt for authentication auth-user-pass credentials.conf in the opevpn folder I have a credentials.conf file with user/pass
-
[Support] binhex - DelugeVPN
ok so I downloaded the latest cert and tested it on the Linux host running docker and I am able to connect to the VPN successfully
-
[Support] binhex - DelugeVPN
whats interesting about SlickVPN is there is no zip file to download, you download a single .ovpn file remote gw1.ams2.slickvpn.com 443 udp # host/port of vpn server # prompt for authentication auth-user-pass credentials.conf # equivalent to pull, tls-client client # redirect all outgoing traffic to the vpn gateway redirect-gateway # verify the server certificate for authenticity remote-cert-tls server cipher AES-256-CBC proto udp dev tun keepalive 10 120 nobind persist-key # ssl certificate / key used for tls #ca certs/ca.crt <ca> -----BEGIN CERTIFICATE----- MIIDQDCCAqmgAwIBAgIJAM8Brk2pUr0KMA0GCSqGSIb3DQEBBQUAMHQxCzAJBgNV BAYTAlVTMQswCQYDVQQIEwJDQTEMMAoGA1UEBxMDVlBOMQwwCgYDVQQKEwNWUE4x DDAKBgNVBAsTA1ZQTjEMMAoGA1UEAxMDVlBOMQwwCgYDVQQpEwNWUE4xEjAQBgkq hkiG9w0BCQEWA1ZQTjAeFw0xMjAzMDMwMjExNDJaFw0yMjAzMDEwMjExNDJaMHQx CzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEMMAoGA1UEBxMDVlBOMQwwCgYDVQQK EwNWUE4xDDAKBgNVBAsTA1ZQTjEMMAoGA1UEAxMDVlBOMQwwCgYDVQQpEwNWUE4x EjAQBgkqhkiG9w0BCQEWA1ZQTjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA wY2K08N7or1Br/EsD9XBon7gs7dKflWYuymgMLJfeMFWuJloNdsn+3GARIhYBbN6 zhvFGFE214qKPqAydW1WmIIK7KoC0sgndr+Vk/au9gssFzVmmvr6+WN/nfo2L9Kv vBMoYLrMAiyw/D4cRapZi2pXJLcMDfC+p1VWAX8TYWkCAwEAAaOB2TCB1jAdBgNV HQ4EFgQUmyvO4rTnu5/ABnp0FngU+SdR8WAwgaYGA1UdIwSBnjCBm4AUmyvO4rTn u5/ABnp0FngU+SdR8WCheKR2MHQxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEM MAoGA1UEBxMDVlBOMQwwCgYDVQQKEwNWUE4xDDAKBgNVBAsTA1ZQTjEMMAoGA1UE AxMDVlBOMQwwCgYDVQQpEwNWUE4xEjAQBgkqhkiG9w0BCQEWA1ZQToIJAM8Brk2p Ur0KMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADgYEAoB0kOuGvrzPBTIRX IDHCCxBMdny+3sKAOllmH4+51j2aWhAJ4Pyc/yBTYyQGNoriABjmNzp+R05oiaxA D3vTgR80juKDPtQb8LoGLBF18gL7Vtc3+hJXcJasXZaDSSoyh5f+TtGvytIT+ece JWIrKnFXzlHOvKlyLkcZn15gwKQ= -----END CERTIFICATE----- </ca>
-
[Support] binhex - DelugeVPN
I've done that, and apt autoremoved any unused packages on ubuntu....
-
[Support] binhex - DelugeVPN
any recommendations on where to troubleshoot?
-
[Support] binhex - DelugeVPN
docker container just stopped working today, only thing that has changed about my environment is the recent install of Netdata on the host machine. docker-compose logs attached for delugevpn deluge logs
-
[Support] binhex - rTorrentVPN
also having recent issues with delugevpn image. Seems this could possibly be related to recent install and uninstall of Netdata, but unsure. Suddenly it just wont connect deluge logs