Closed trireme32 closed 2 years ago
PIA DNS issues, please set NAME_SERVERS to the following:-
84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
After updating the DNS, no longer getting network errors, instead getting
Unable to successfully download PIA json to generate token for wireguard from URL 'https://privateinternetaccess.com/gtoken/generateToken'
Seems to still be a PIA issue?
Seems to still be a PIA issue
Most probably yes, try another endpoint
Most probably yes, try another endpoint
Have tried nl-amsterdam, all the CA- ones, swiss- ,sweden-,uk-,monaco- none of them work so seems to be a widespread token generation issue.
Any way to monitor the status of it without manually restarting the container again and again hoping it connects?
Any way to monitor the status of it without manually restarting the container again and again hoping it connects?
just leave the container going it will continually retry, look in /config/supervisord.log to confirm its working or try the web ui, once the web ui is accessible you know the connection to the tunnel has been established.
just leave the container going it will continually retry, look in /config/supervisord.log to confirm its working or try the web ui, once the web ui is accessible you know the connection to the tunnel has been established.
This is the end of the code in log file, seems that the start script exits after failing the 12 retries and stops trying to reconnect.
2021-11-07 15:42:47,288 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://privateinternetaccess.com/gtoken/generateToken'
[info] 2 retries left
[info] Retrying in 10 secs...
2021-11-07 15:43:05,815 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://privateinternetaccess.com/gtoken/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...
2021-11-07 15:43:15,816 DEBG 'start-script' stdout output:
[crit] Unable to successfully download PIA json to generate token for wireguard, exiting script...
2021-11-07 15:43:15,817 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22646109341968 for <Subprocess at 22646109341296 with name start-script in state RUNNING> (stdout)>
2021-11-07 15:43:15,817 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22646109458640 for <Subprocess at 22646109341296 with name start-script in state RUNNING> (stderr)>
2021-11-07 15:43:15,817 INFO exited: start-script (exit status 1; not expected)
2021-11-07 15:43:15,817 DEBG received SIGCHLD indicating a child quit
hmm ok i thought i put in an infinite loop, its been a while sice i have stared at that particular code tbh, in any case i thought i would restart my container and for me i have no issues getting a pia token issued or a port assigned, this is for endpoint nl-amsterdam.privacy.network
using wireguard, so not sure why you are seeing an issue, perhaps try the same endpint and check your subscrption hasnt expired
hmm ok i thought i put in an infinite loop, its been a while sice i have stared at that particular code tbh, in any case i thought i would restart my container and for me i have no issues getting a pia token issued or a port assigned, this is for endpoint
nl-amsterdam.privacy.network
using wireguard, so not sure why you are seeing an issue, perhaps try the same endpint and check your subscrption hasnt expired
Seems to have just come back online, just restarted the container without changing anything and now even the ca-ontario server is working properly
PIA DNS issues, please set NAME_SERVERS to the following:-
84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
just wanted to ask a question regarding this fix(meaning it worked for me), doesn't this create a dns leak? it seems to based on the test i ran, but how concerned should someone be about that?
NS lookup can only be performed over the VPN tunnel due to iptables therefore ensuring no ip leakage.
If of course you are using privoxy for your test then this will be the issue, privoxy is a HTTPS proxy only, i.e. name lookups will be sent over your ISP's connection.
Synology docker container, latest.
All was working fine as of yesterday. When I went to open Deulge today, I noticed nothing was happening, so I restarted the container. Got the info below. Tried resetting the container, and rebooting the system. Same error every time.
That last part repeats a number of times and then it exits.