Protonvpn connection issue
 

I'm using the protonvpn-cli-2.2.11, because I can and very much want to go around networkmanager. I'm a slackware64-15.0 user, so I don't have to suffer that <...sentence deteriorates into expletives:)>. I can take it or leave it.

I connect via the protonvpn script added to the init scripts (Yes, no systemd) and run the protonvpn-cli to connect. It modifies the route, & etc/resolv.conf. Protonvpn-cli has one short script in /usr/bin and is otherwise much like a python module with small scripts aplenty.

Occasionally, the vpn is liable to hang, In this state, I can't browse. Curiously, running downloads will complete. /etc/resolv.conf sometimes has gone back to it's 'no vpn' state. other times it looks connected. 'Route' throws up the headers, pauses 5-10 second and shows me connected to the vpn. But I'm not. The script has a 'status' option which shows me connected. But if I reconnect, my browsing is fine - until the next time, whenever that is. It might happen 3 times in a morning, the be ok for weeks. Suspending my pc does it reliably.

Any fixes, guesses as to the issue, or tests to narrow this down are welcome and will be tried.

Hi,
Don't use this specific vpn software but does it have a debug mode?
That would be handy.

No debug mode. It's a bunch of python scripts which are a remake of a bash script and probably added a few options. It does have the advantage that I can choose my exit point. My transfers are encrypted until the vpn exit point. So a local server in a small country mightn't offer as much protection as say an Australian or Japanese one.


EDIT: I don't actually need protection currently, but may need it some day.

Good news, there is a way to debug if still valid
https://github.com/ProtonVPN/protonvpn-cli/issues/92

Look into the scripts for where it calls the executable and modify it?

Hmmm.

I checked that site. I'm using the python rewrite of the bash script protonvpn-cli.sh.

You'd hardly call a python script '.sh' would you? I think this is the github site
https://github.com/Rafficer/linux-cli-community bacause IIRC that's what I built in the slackbuild (if there was a slackbuild). I threw this thing together one afternoon anyhow, and honestly don't remember how.

But I never checked that github site for a relevant issue, or posted one. I'll go that road, and report back.

EDIT: Just thinking: Bash scripts are clunky, but might be better than a dodgy python mess. Only, I can't log into github ATM because my email server is offline - again! I have email verification set up on github. As soon as I can get in, I'll drop that email and switch email provider. It's been three days now and they don't care or won't pay the ransom :(.

www.mail.com works. My password is accepted, and I'm transferred to login.mail.com, which times out.

Now it's going out to lunch again... I'm checking stuff.

• /etc/resolv.conf has no vpn lines - just my standard stuff. It thinks I'm disconnected.
• route takes 5 seconds but throws out vpn lines. It thinks I'm connected.
• dig responds.
• whois doesn't respond, or the browser.
• protonvpn status goes out to lunch. No timeout.

I issued a 'reconnect' command. It replied I'll chase the Issues on that site I posted, or post one myself. I can get into my mail by using a NY vpn server, so it thinks I'm from the States.

I'll try tomorrow on that github site. It's late here

Okay. This has taken an unexpected turn.

The problem got drastic. I disconnected the vpn by habit, and the problem persisted. I rang my isp, and they did their "look-up-the-router" trick. That seemed good. I pinged my dns server and it timed out. He asked me to try a different pc, so I dragged myself off to my RazPi and that was fine.

I'll post the network issue as a new thread. If the vpn issue persists, I'll mark this unsolved and update.

I use ProtonVPN, it never crossed my mind to use their script. I simply fire up openvpn and use the config(s) I downloaded from Proton.

Edit: But I use my own private DNS, I do not need theirs.

I seem sorted at this stage. Don't know what it was, maybe a disk issue but I restored a backup and sorted it that way.