New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevents Login To Vonage #2104
Comments
Hello! Could you provide the debugging information requested in https://github.com/EFForg/privacybadger/blob/1cac5ba752517802d0596645c464ffd55a60c9d0/.github/ISSUE_TEMPLATE/broken-site-report.md? |
Is the problem domain in question |
The problem is with the domain app.vonage.com. |
Would it be possible to ask a customer whose Badger learned to block "vonage" to run the same debugging code in their Badger, and share the output here? My guess at this time is that we should tell Privacy Badger |
It happens to others at the office, no need to ask a customer. If you can
ignore app.vonage.com it’ll be great.
…On Wed, 8 Aug 2018 at 18:47 Alexei ***@***.***> wrote:
Would it be possible to ask a customer whose Badger learned to block
"vonage" to run the same debugging code in their Badger, and share the
output here?
My guess at this time is that we should tell Privacy Badger vonage.com
and vonagebusiness.com belong to the same entity, but I don't know if
there is more to this problem than just these two domains.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2104 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhFIzUwoBANLPoMTBym2pve6mZztU7eUks5uOwglgaJpZM4VWS3j>
.
|
Could you have somebody who is experiencing this issue run the debugging code in their Badger and share the output with us? |
And what if you do the same thing, but for |
Users with the Privacy Badger Chrome/Firefox/Opera extension can't log into our app at app.vonage.com.
The text was updated successfully, but these errors were encountered: