Jump to content

Recommended Posts

Posted

I make payments online. However since the last ESET update, I am not able to make payments to one site. I can make the payment in Google Chrome on its own. But once I use the payment protection facility, it tells me:

Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
 
But I am not sure HOW to do this.
  • I followed the suggestions after doing a GOOGLE SEARCH. I made the network protection setting INTERACTIVE. but I am not sure whatelse to do.
  • I have been making these payments without a problem until the last ESET UPGRADE.

Can anyone help?

Please write in 'plain English'  when you reply....I do my best but technology can be challenging.

I look forward to a speedy response...the bill is for my internet provider... so it is a bit urgent since the bill is now overdue.

Cheers,

Celia

 
Posted

Does this occur only on the web site mentioned when using Chrome and Eset Banking & Payment protection? Or, does this same behavior occur on other web sites when using Eset Banking & Payment protection?

Posted

Only with this site. The other site works. The message says he site refuses to connect and then gives me options which I tried ...but they did not work.

Look forward to hearing from you soon.

Cheers,

C

  • Administrators
Posted

I would recommend opening a ticket with your local ESET support and provide step-by-step instructions how to reproduce the issue. Also enclose logs collected with ESET Log Collector please.

Posted

Thanks, not sure how to do that. I bought my licence on the US site but I live in the Caribbean. The last time I had an issue I tried to ask from the US site since that is where I bought my licence and they said I had to contact someone locally. Since I have not dealt with anyone locally I did not know who to contact. So just left it. I got a computer person to sort it out. He used another virus programme and sorted it out.

This is now getting confusing...I will have to search around to see what else is available that is less confusing....unlikely that I will renew. I may just try another provider. I recommended another person and they bought it... but I donot know anymore.

I could not find where to ask a question other than this forum...which is why I asked the question here.

So Be it.

Thanks for your suggestion,

C

  • Most Valued Members
Posted
9 minutes ago, celia said:

Thanks, not sure how to do that. I bought my licence on the US site but I live in the Caribbean. The last time I had an issue I tried to ask from the US site since that is where I bought my licence and they said I had to contact someone locally. Since I have not dealt with anyone locally I did not know who to contact. So just left it. I got a computer person to sort it out. He used another virus programme and sorted it out.

This is now getting confusing...I will have to search around to see what else is available that is less confusing....unlikely that I will renew. I may just try another provider. I recommended another person and they bought it... but I donot know anymore.

I could not find where to ask a question other than this forum...which is why I asked the question here.

So Be it.

Thanks for your suggestion,

C

I would have thought the support would have been where you bought it from regardless of your location now but maybe I'm wrong.

Another option is to check the firewall troubleshooter which might help to see if something is being blocked 

Posted

The problem here is not that Eset firewall is blocking access for Chrome. If this was the case, the OP would be receiving the same message from Chrome when not using Eset Banking & Payment Protection. More puzzling is it appears this only occurs on one web site when using B&P?

Something like this has never been posted in the forum as far as I am aware of. There have been previous issues with using Chrome and B&PP but that affected all web site access; not just one site. Finally, the OP indicated this issue just manifested after upgrade to Eset ver. 13.2.15.

This issue is not something that is going to be resolved in this forum and will probably need to be researched by Eset personnel. Open a technical support request as shown in the below screen shot. Briefly describe the issue an post a link to this forum thread in the request. Also include "Details for technical support" in the reply as shown on the screen shot.

Eset_Tech_Support.thumb.png.1b640d2fe4827162aebeaf849a95ed20.png

 

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...