I am running Windows 10 on an HP Elitebook 8440P and get the following error:
"An error has occurred initializing the VPN: Post http://localhost:7171/firewall/stop: dial tcp [::1]:7171: connectex: No connection could be made because the target machine actively refused it."
Hi @inclusivity. thanks for your report. and that is indeed a quite original way of bumping the issue :)
To your question: we're working on other prioritary issues. we do what we can with limited time and resources.
from the description you provided I cannot form an idea of what the problem is. The mention to "can't login" is confusing to me, because no registration or sign-in is required in RiseupVPN.
after the crash you mention, does the application refuses to start?
Hey Kali, my apologies about the language, I edited that. Thanks for getting back so quickly. So yeah, like every-time I start up my computer and try and run the VPN program that message comes up?
Funny that the error is talking about the firewall, we haven't implemented yet a firewall for windows. You should be able to ignore the error (sure, have to make sure it doesn't appear again).
Does the VPN connect? The logs seems to say that it connects correctly and the error pops up when you turn it off.
Avira Free Antivirus: Malware found: The pattern of 'HEUR/APC (Cloud) [HEUR/APC]' detected in file 'C:\Program Files\RiseupVPN\bitmask_helper.exe. Action performed: Move file to quarantine.
Even if moved out of quarantine, it cannot be placed into the RiseupVPN folder (permission denied).
after clean uninstall (riseupVPN folder also deleted) installation fails:
RisupVPN Setup: Error opening file for writing: C:\Program Files\RisupVPN\bitmask_helper.exe Click to Abort to stop the installation, Retry to try again, or Ignore to skip this file.
Hi !
I'm also having same issue : "http://localhost:7171/firewall/stop: dial tcp [::1]:7171:". Maybe an answer track. I had no problem with riseupVPN when I installed it. After, I changed my antivirus from kaspersky to Clamwin, riseupVPN no longer worked. It might help.
I tried to uninstall, reinstall. It solved the problem for me. At least temporarily.
update : at least temporarily. it doesn't works anymore. same issue.
hi all - we are working on this. we are testing a new beta release that might help with this issue, but I want to make sure it is not going to make the problem worse. This new version won't use nssm to install the service, so my guess is that antivirus won't find it "guilty by association" (since other programs classified as malware also uses nssm). Anyway, just a heads up, it's likely we upload something later today or tomorrow.