Merijeek
-
Posts
129 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Merijeek
-
-
...can anyone give me some insight as to what might have caused this to start up today?
2016-10-08 20:59:57,882 DEBG 'start-script' stdout output:
Sat Oct 8 20:59:57 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected]
Sat Oct 8 20:59:57 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
Sat Oct 8 20:59:57 2016 TLS_ERROR: BIO read tls_read_plaintext error
Sat Oct 8 20:59:57 2016 TLS Error: TLS object -> incoming plaintext read error
Sat Oct 8 20:59:57 2016 TLS Error: TLS handshake failed
-
So, I'd been running for some time without issues. I went ahead and allowed an update (no, I don't know why...) and now I can't get a connection.
Log file is showing me:
2016-10-08 16:03:30,788 DEBG 'start-script' stdout output: Sat Oct 8 16:03:30 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Sat Oct 8 16:03:30 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Sat Oct 8 16:03:30 2016 TLS_ERROR: BIO read tls_read_plaintext error Sat Oct 8 16:03:30 2016 TLS Error: TLS object -> incoming plaintext read error Sat Oct 8 16:03:30 2016 TLS Error: TLS handshake failed
Any suggestions what I've got going on here?
-
Hi all -
I just had to wipe my dockers. Usually not a big deal, but they tend to go spastic on me after a couple weeks. Fortunately I've got my configs stored, so usually it isn't a problem. I just paste the config back into the CLI and off I go. But not now.
Here's my config:
docker run -d \
--cap-add=NET_ADMIN \
-p 8112:8112 \
-p 8118:8118 \
--name=delugevpn \
-v /mnt/user/Incoming:/data \
-v /mnt/user/config/delugevpn:/config \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=yes \
-e VPN_USER= \
-e VPN_PASS= \
-e VPN_REMOTE=nl.privateinternetaccess.com \
-e VPN_PORT=1194 \
-e VPN_PROTOCOL=udp \
-e VPN_PROV=pia \
-e ENABLE_PRIVOXY=yes \
-e LAN_NETWORK=192.168.1.0/24 \
-e DEBUG=false \
-e PUID=0 \
-e PGID=0 \
binhex/arch-delugevpn
I've obviously cleared my user and pass.
What I'm getting in my logs as a try and fail to connect is:
2016-07-20 21:56:44,219 DEBG 'start-script' stdout output: Wed Jul 20 21:56:44 2016 SIGUSR1[soft,tls-error] received, process restarting 2016-07-20 21:56:46,238 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 UDPv4 link local: [undef] Wed Jul 20 21:56:46 2016 UDPv4 link remote: [AF_INET]46.166.190.207:1194 2016-07-20 21:56:46,412 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-07-20 21:56:46,597 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Wed Jul 20 21:56:46 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Wed Jul 20 21:56:46 2016 TLS_ERROR: BIO read tls_read_plaintext error Wed Jul 20 21:56:46 2016 TLS Error: TLS object -> incoming plaintext read error Wed Jul 20 21:56:46 2016 TLS Error: TLS handshake failed 2016-07-20 21:56:46,597 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 SIGUSR1[soft,tls-error] received, process restarting 2016-07-20 21:56:48,616 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 UDPv4 link local: [undef] Wed Jul 20 21:56:48 2016 UDPv4 link remote: [AF_INET]46.166.190.233:1194 2016-07-20 21:56:48,792 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-07-20 21:56:48,970 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Wed Jul 20 21:56:48 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Wed Jul 20 21:56:48 2016 TLS_ERROR: BIO read tls_read_plaintext error Wed Jul 20 21:56:48 2016 TLS Error: TLS object -> incoming plaintext read error Wed Jul 20 21:56:48 2016 TLS Error: TLS handshake failed
So...any idea what's up? And why I'm seeing a self-signed cert from Columbus Ohio? I don't have logs from before, but I'm thinking the Cleveland thing isn't normal.
-
Well, it appears (For reasons I'll never know) that a reboot of the container took care of that for me.
Of course, it also changed my VPN IP which caused other headaches, so I guess the solution is "don't reboot it too often". I have the feeling PIA won't give me a way to always land on the same external IP.
-
As far as your tracker showing connectable, is that something on their site? Or is it something that shows somewhere in Deluge?
I'm looking using their site, which shows not connectable. Is there somewhere I should be checking in Deluge?
-
Yes, I have two seeding but I'm still not showing connectable.
The only thing I'm really seeing in the log is this repeating every 5 minutes:
2016-05-15 10:25:44,757 DEBG 'deluge-script' stdout output:
[info] Deluge incoming port 43265 open
[info] Sleeping for 5 mins before rechecking listen interface and port (port checking is for PIA only)
-
Yup, I'm using nl.privateinternetaccess.com. I'm going to take a wild guess and say that's Netherlands.
-
Hmm. Still an issue. According the DelugeVPN I'm at 43265. Now, I believe that is that, I shouldn't need to allow anything over on the PIA portal or anything.
So...should that be that? Or is there a step I'm missing? According to my tracker I'm not connectable, and according to http://www.yougetsignal.com/tools/open-ports/ my PIA's IP isn't available at that port.
-
Check the log. Right. My wife is right, I do keep getting dumber.
-
If it's a torrent that has been inserted by Sickrage, everything works perfectly. Torrents come in, files go out into the proper media directories. Only complaint here is that Sickrage doesn't seem to know how to let a torrent sit a bit before moving it away, which obviously breaks the seeding.
Can you not set sickrage to copy the file instead of move it? I can at least do that in sonarr.
I did that now, thanks for the idea. I guess it means I'll just have to manually clear them out occasionally. But still, at least they don't go away instantly.
-
What should be a silly simple question that I can't find an answer to...
I'm using DelugeVPN with PIA - and I can't figure out where to find what port I'm forwarding, if I am forwarding one.
Can anyone remind me where to look?
-
Well, that didn't help much.
Near as I can tell, everything either ends up as:
drwxrwxrwx 1 nobody users
and is fine, or ends up:
drwxr-xr-x 1 root root
Which means I can't do anything with it via Windows, though I can do it from UnRAID CLI since, obviously, I'm logged in as root.
After running the "New Permissions" tool those same folders are:
drwxrwxrwx 1 nobody users
-
I had a few credentials I deleted just to be thorough, but there were none for the Unraid server.
All my shares are, for the moment, public shares, so I never get asked for credentials.
I'm waiting on Sickrage to download something, at which point I'll see who that file's owner is.
-
The ones that were added by me via the AutoAdd.
The Sickrage ones are fine.
-
Hi all -
I was just pursuing this in the general support thread and was told I should look here.
I've basically got an issue with DelugeVPN.
There are two ways I get torrents into it - via Sickrage, or via me dumping a .torrent file into an auto add folder. Both of these work as they should.
If it's a torrent that has been inserted by Sickrage, everything works perfectly. Torrents come in, files go out into the proper media directories. Only complaint here is that Sickrage doesn't seem to know how to let a torrent sit a bit before moving it away, which obviously breaks the seeding.
However, the BIG problem is just plain torrent downloads. After the download is complete, and I want to move the file (via Windows), I can't. I get a "You require permission from UNRAID\root to make changes to this file".
Checking the file ownership I'm getting:
Any suggestions on how I can make these files not owned by root? Currently, I'm having to go under Tools and do the "New Permissions" command. Which works, but is obviously annoying.
-
I seem to have an issue with DelugeVPN refusing to shutdown. I tell it to restart, and it doesn't. I tell it to shut down, it doesn't. I try to kill it via command line, and the command runs and the command line just sits.
Further, when I do that it SEEMS (not confirmed 100%) to then knock the GUI offline, and I can't even reboot the unRAID box from the CLI.
Anyone seen anything like this? Any idea how I could have something misconfigured here?
-
I've got what I'm hoping is a simple question here.
I have had two forced reboots (hardware issue that I think I have resolved) but when I get everything running again, and I finally get to the point where I can get into DelugeVPN, my Deluge settings seem to be gone and I have to recreate them.
Is there some sort of commit or something I need to do to get my settings to stick in the event of a reboot?
[Support] binhex - DelugeVPN
in Docker Containers
Posted
Has something gone funny with PIA?
My installation (which I C&P when needed) looks like this:
However, the VPN is failing over and over because of a self-signed cert in the chain.
I'm at a loss as to what to do here. It's not like I can do anything about PIA's cert chain. Is it possible to skip the verification? And even if I could, would I want to?