Can no longer connect with Comodo enabled

[wildbill 0]

Have the settings required for Comodo changed in the last week or so?  The last time I tried to connect with the arivpn client I didn't have any issues when comodo was enabled.  Now a week or so later I can only connect if I disable comodo.  The FAQ doesn't appear to have been updated.  I did do a comodo upgrade last time I connected, but it looks like all the rules are still in place.  Any ideas why comodo would suddenly be blocking the airvpn client from connecting if I haven't changed comodo's rules or settings?

[poldi23 1]

Hello,

I am experimenting the same issue for about a week too - on two computers running Windows 7 Enterprise 32 bit and 64 bit.Both computers have been setup like in the HowTo explained and they have been working for MONTHS with the AirVPN client. I have to say, that SOMETIMES I can connect, using the AirVPN Client. I know it sounds strange.
I did not try running the computer without Comodo!

Issue explained:
When using the AirVPN Client trying to connect, I get an error message: the remote server returned an error(502)Bad gateway.
ALSO: Usually I could connect to the airvpn website - even if I did not use the AirVPN service, which is correct, as stated in the HowTo. This is not the case anymore.

Now, using only the OpenVPN Gui and the special setup, I can connect to the internet.
Special setup means: inside the "config folder" of OpenVPN (C:\Program Files\OpenVPN\config) I put the, on the AirVPN website created  .ovpn  files for each server, into the folder.
Checking the http://ipleak.net/, I see that, I am connected through AirVPN - seeing a different IP address and the statement, that I am connected to an AirVPN exit node.

I AM EXPECTING, THAT I AM SAFE ! RIGHT?

Any help is much apprichiated.

[SlyFox 10]

I am also using the latest comodo as well and have no problems. But I only use rules for my torrent client to prevent leak. What rules do you have set up specifically?

[wildbill 0]

Well I found out something interesting from experimenting.  I only need to disable Comodo so the airvpn client can log in and connect to one of the servers.  Once the airvpn client is done "Checking" I can re-enable Comodo and everything works as it did before this problem started.  It appears the only thing that doesn't work is whatever the airvpn client is connecting to when you try to log in.  Oh I also have to disable Comodo in order for it to successfully disconnect.

 

I set the rules up like it said in the FAQ and I haven't changed them in over a year since I first set them up.  I recently downloaded the updated airvpn client, but it did work after that with no problems.  It worked as recently as about a week to 10 days ago.  I hadn't used it since then until yesterday when it didn't work.  I don't know if the Comodo update I had done that last time caused this or if something else changed with airvpn.

 

I'm ok with the workaround but I'd rahter not have to disable Comodo to log in or log out because I didn't used to have to do that.

[L0bstrosity 0]

Yes, something has changed with the last Comodo update...I can no longer connect through OpenVPN with Comodo enabled using the same rules I have been using for many months now.  Digging through log files now to see what's going on.

 

**Update**

 

Well spoke too soon when blaming it on Comodo...The entry server IP had changed so I just needed to update my Comodo rules...Woops.

[poldi23 1]

Would you please let us know, what settings you have changed, so it´s working again?

Thanks !

[Staff 10128]

  On 5/11/2014 at 2:41 PM, user 1a said:

Would you please let us know, what settings you have changed, so it´s working again?

Thanks !

 

Hi,

 

we changed nothing on this respect.

 

Kind regards