www.chase.com

[adguard-bot]

Issue URL (Incorrect Blocking)

https://www.chase.com/

Comment

Note that I already have AG “protection disabled” on Chase.com, but it still prevents the site from loading normally and also blocks log in completely. It just glitches out if I try to log in with the AG extension turned on. If I turn it off in the “Manage Your Extensions” panel, then the site loads normally.

The Home page auto-redirects to screenshot #1 with the AG extension turned on. This just started happening sometime within the past 2 days. Username: @shape55

[NSFW] Screenshots

Screenshot 1

[Screenshot 1](https://cdn.adguard.info/sitereports/i7iq03hlv1ck4gg4gsosg0s80o4oskclowrdn5v0dc.png?nc=1)

Screenshot 1 with AdGuard disabled

[Screenshot 1](https://cdn.adguard.info/sitereports/ik3tjmk3xzsccooco0w84so4ccggkksfidn45y7a9w.png?nc=1)

System configuration

Information	Value
AdGuard product:	AdGuard Browser Extension v4.2.241
System version:	Mac OS 10.15
Browser:	Firefox
Stealth mode options:	Strip URLs from tracking parameters, Hide your search queries, Send Do-Not-Track header
Filters:	Ad Blocking: AdGuard Base, AdGuard Mobile Ads Privacy: AdGuard Tracking Protection, AdGuard URL Tracking, EasyPrivacy, Fanboy's Enhanced Tracking List, Legitimate URL Shortener Social Widgets: AdGuard Social Media Annoyances: AdGuard Annoyances, AdGuard Cookie Notices, AdGuard Popups, AdGuard Mobile App Banners, AdGuard Other Annoyances, Adblock Warning Removal List, I don't care about cookies Security: Online Malicious URL Blocklist, NoCoin Filter List Other: Filter unblocking search ads and self-promotion Language-specific: AdGuard Russian, AdGuard German, AdGuard Japanese, AdGuard Dutch, AdGuard Spanish/Portuguese, AdGuard Turkish, AdGuard French, Official Polish filters for AdBlock, uBlock Origin & AdGuard, AdGuard Chinese, EasyList Czech and Slovak, EasyList Italy, Liste AR, List-KR, Persian Blocker, Polish Anti Adblock Filters, Dandelion Sprout's Nordic Filters

[shape55]

I don't know how the [NSFW] option got enabled. I didn't touch it.

[piquark6046]

https://github.com/AdguardTeam/AdguardFilters/issues/170006#issuecomment-1879319719 It is a bug of AdguardTeam/ReportsWebApp.

---

@shape55 Did you access the webpage via the following URL or similar one? https://secure07b.chase.com/web/auth/dashboard#/dashboard/overviewAccounts/overview/index

[shape55]

Thanks for confirming. No, I accessed the login screen from the Home page at chase.com, but then it immediately auto-redirected to that URL without me clicking the login button, which also shouldn't happen. So it forces you to log in before being able to view/access the site. But the login also fails to complete when the AG add-on is enabled.

[piquark6046]

Can you tell me where is your region or country? And, did you connect to a VPN server?

[shape55]

I'm in the Northeastern US. No VPN used.

[piquark6046]

It seems that you enable Hide Referrer from third parties in stealth mode and your issue is related to https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2648. Please disable the until the issue is resolved if the option is enabled.

[piquark6046]

@shape55 Do you enable the option, and does disabling the option resolve your issue?

[shape55]

Hi, yes, this works and allows the site and login to load normally – thanks. However, I already had Chase disabled in the AG blocker window, which I expected to have bypassed all toggle settings. Does this enable/disable setting and the allow list only bypass the Filters section?

[piquark6046]

It seems that any filter does not affect your issue and it is caused by Hide Referrer from third parties in stealth mode.

[shape55]

Yes, that I understand. But why doesn't disabling AG for Chase in the toolbar icon's blocker window (or adding it to the Allowlist) bypass all toggle settings? Isn't this how it's supposed to work?

[piquark6046]

I can create a rule disabling only Hide Referrer from third parties for the website. But, The rule does not work currently because of a bug of AdGuard Browser Extension.

[shape55]

I see. I'll just have to wait then. But I have to keep this setting disabled for all sites now rather than just Chase, b/c disabling AG for Chase only doesn't deactivate this setting, and therefore does not circumvent the bug which prevents the site from loading.

What I was trying to clarify before was if this is intended behavior for the setting, or is it supposed to be disabled on sites that are whitelisted? If the latter, then which other settings remain enabled on whitelisted sites?

[piquark6046]

I guess that allowing the website entirely in AdGuard does not disable the stealth option for the website because of the bug. I think that you should disable the stealth option until the bug is resolved if you want to visit the website.

[shape55]

Right, ok – but normally I assume that this Hide referrer setting is also supposed to be disabled on whitelisted sites.

Yes, I have kept this Stealth option disabled after your first response that stated it was a bug. Thanks

[piquark6046]

Is it okay to close the issue?

[shape55]

Are bug reports normally closed before being fixed? I thought they are kept open until resolved.

[Alex-302]

@shape55 Please check with 4.3.13 I can't register - buttons do not work.

[shape55]

Hi, I re-enabled the Hide referrer setting in 4.3.13, but now the same issue is happening again. You actually don't need to login to test it though. As I explained above, this bug prevents me from being able to login. It affects the login window, expanding it to fullscreen (see screenshot 1), blocking out the rest of the site as well as the login process.

[Alex-302]

@shape55 Hi Please test with this rule @@||secure.chase.com/web/auth/$stealth

[shape55]

Yes, this rule works! Thanks :slightly_smiling_face:

[Alex-302]

Ok, added

[shape55]

So this will be added to the next AG app update then, or filter update?

[Alex-302]

With the Base filter update.

[shape55]

Hi, the same problem w/ Chase.com is back. So I added the user rule you provided above until it's fixed again.

[Alex-302]

Weird. Current rule must work.

[shape55]

Not sure what you mean. Were you able to reproduce it? Will it be fixed in the next Base Filter update again?

[Alex-302]

Not sure what you mean. Were you able to reproduce it? Will it be fixed in the next Base Filter update again?

I can't reproduce.

In the base filter we have @@||secure.chase.com/web/auth/$stealth=referrer

[shape55]

Hmm, that's strange. It's been working fine on my end with the rule removed from User Rules all this time, but I just started getting the error again 5 days ago. I tested it several times: if I disabled the AG add-on in Firefox, the sign-in worked normally, but if I enabled it (w/out the user rule manually entered) then I'd get the same glitchy behavior as before that blocked my log in.

[shape55]

Hi, a totally different issue just started happening since my last log in. The entire site of chase.com is nonfunctional w/ AG enabled. Nothing loads or responds to clicks unless I turn off AG completely using the Pause button. The rule still works for the log in page, but the rest of the site is unusable w/ AG enabled – and I haven't change a thing on my end.

[Alex-302]

@shape55 Please test these rules one by one

@@||chase.com^$content
@@||chase.com^$urlblock
@@||chase.com^$genericblock
@@||chase.com^$elemhide
@@||chase.com^$generichide
@@||chase.com^$specifichide
@@||chase.com^$jsinject
@@||chase.com^$extension
@@||chase.com^$stealth

[shape55]

Hi, did you already change something, b/c I haven't changed anything in Firefox yet the site is loading & responding again now w/ AG enabled.

[Alex-302]

@shape55 No, did not change rules for this site. Maybe caused by another extension and it was updated? Do you use release or dev/beta channel of browser?

[shape55]

Very strange then, b/c I tested it about 4 times to make sure this was the cause. AG on: Chase pages wouldn't load (even if the toggle switch was turned off for Chase). AG off: Chase pages loaded normally. And I haven't updated the browser either, nor did I test other extensions b/c this was the first one I tried. Since the site worked when AG was disabled, I didn't check any others.

I always use the release version of Firefox, and update it from the "About Firefox" window. Anyway, I'll retest it some more this week, and see if anything changes. Thanks

[shape55]

Chase.com is still working ok, so I'm not sure what part of AG was causing the issue before – but it was even preventing the UI from loading, rendering the whole site unusable. It could have been a 3rd party filter, where an auto-update fixed it – just speculating.

Also, I disabled the rule you gave me for the login window, and it's working ok without it. So I guess this was fixed in an update. Thanks

[Alex-302]

I guess recent problems were caused not by AdGuard.

[shape55]

Well, to clarify what I explained in the previous message though, the only time Chase wouldn't load before was with AG enabled. The only single thing I tested was AG, and when I disabled it, it loaded normally. And I tested this scenario on/off 4 times. That's all I know for certain, and that it's working normally again now.

[shape55]

Update: I'm having to use the stealth rule you gave me for the Chase.com login window issue again, or the same thing occurs as did previously.

While the most recent issues mentioned above with pages not loading/responding normally must have been fixed in a filter update, a new issue is occurring with the “Pay Card” button, where it now won't open if clicked. If I check the Blocked or Modified tabs in AG's Filtering Log, nothing shows up though, so I'm not sure how to track the cause. As of last night, if I disabled Chase.com AG protection with the toggle button, then the Pay Card button worked normally. But when I re-enabled it, then it was blocked and I couldn't access the payment window.

[Alex-302]

@shape55 https://github.com/AdguardTeam/AdguardFilters/issues/170006#issue-2068109351 Do you still use these settings and Firefox?

Could you please export your settings, and test with https://agrd.io/extension_firefox_beta ?

[shape55]

Yes, I haven't modified any settings/toggle switches since I first reported this.

I just exported the settings, then imported them into the new standalone version you linked, disabled the $stealth rule, and retested both issues a few times. The login screen works fine on this version, but I’m still having the same issue w/ the Pay Card button (https://secure.chase.com/web/auth/dashboard#/dashboard/overview/index;flyout=payCard,-666485273,BAC,microApp). However, it’s inconsistent and glitchy: first it worked, then it didn’t work, and the same again when reloading, or logging out/in again. And the “Sign out” button, similar in shape/size to the Pay Card button, now has the same inconsistent behavior in sync w/ the Pay Card button: either both work, or neither work.


Note that this page wouldn’t load for me: https://welcome.adguard.com/v4/chrome/thankyou.html – I just got the spinning progress wheel.

[Alex-302]

It the problems caused by Tracking Protection? With @@||chase.com^$stealth same problems?

[shape55]

I tried disabling the Tracking Protection master switch at the top, and the Pay Card button works now. So it has to be one or more of the 4 "General" toggles that are blocking it. I tried again several times just disabling only the first 2, but AG still blocks both buttons (Pay Card & Sign Out).

To clarify what I explained above, I don't need the $stealth rule for the login screen now, b/c it works normally again w/out it in the Standalone test version you had me download.