Confusing error when provider is down

Recently riseup vpn provider was down for a few days. I tried to start riseup-vpn.launcher snap and it didn't start, after a while I only saw an error popup saying sth like "bitmaskd ist not running" or so. Sorry for the vague problem description I hadn't have the patience to create an issue while it was happening.

assigned to @meskio

I see two problems here here:

• The fact that we just report 'bitmaskd is not running' for several different of errors, and will be nice to be more explicit on what the error is if we can.
• If a gateway is down bitmask should pick up another one. I thought this one was fixed by bitmask-dev!246 (merged).

changed milestone to %RiseupVPN beta

@meskio: Agree on your first point. However, this issue is not a particular gw down, but bitmask-systray not able to talk to the provider API.

I see, I read it wrongly. Then the only problem to solve is the error communication.

added Doing label

I'm unable to reproduce the problem. "bitmask is not running" to me only happens if bitmask is actually not running, or is zombie or something bad with it.

Anyway, it's an issue, as if we can't reach the provider we fail silently while we could notify the user. I'm adding this notification.

added Review Ready and removed Doing labels

mentioned in merge request !16 (merged)

closed via commit 8c3ba3a2

closed via merge request !16 (merged)

I'm unable to reproduce the problem.

Did you try to shutdown (a|cdevs) providers API and tried with bitmask-systray connecting to it ?

Did you try to shutdown (a|cdevs) providers API and tried with bitmask-systray connecting to it ?

Yes, I tried to block the API by editing my /etc/hosts and by disconnecting my dev VM from the net, and both of them give me the error I just make visible by !16 (merged). Any ideas on how can I reproduce more closely your situation?

I'm wondering what was the issue you shaw, I've being following the code and I can't imagine any situation where this message is displayed and bitmaskd is reachable. It could be that the string of the error was misplaced, that has happen a couple of times when the translation strings where out of sync. Or it could be that bitmaskd somehow crashed when the provider was not reachable.

reopened

removed Review Ready label

added Doing label

mentioned in merge request !29 (merged)

added Review Ready label and removed Doing label

closed via merge request !29 (merged)

closed via commit ff36a035

mentioned in issue #62 (closed)