Another problem with Citibank site

[ron_1]

Posting this on the Linux board, even though I don't think it's a Linux-type issue. Ever since Monday, Dec 23, I can't access the Citibank website. I get the login screen, but when I try to login I get a screen that says: "We're sorry. Citi.com is temporarily unavailable." It's weird, because this only started on the 23rd, and I've had 28.8.0 since the day it was released. And yes, I've tried it in a new clean profile, and it still doesn't work. However, it does work in Basilisk. Should I try modifying the UA override for Citi? If so, what should I change it to?

EDIT
I tried changing the UA override to:

Code: Select all

Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 (Pale Moon)

but that didn't work.

[Night Wing]

Have you tried this over ride code?

Code: Select all

Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

[ron_1]

That didn't work either, but thanks anyway Night Wing. Any other suggestions?

[back2themoon]

Try Windows overrides:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9 PaleMoon/28.8.0
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:4.4) Goanna/20170101 PaleMoon/28.8.0
Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

...and so on. These are some of PM's in-built overrides.

[ron_1]

None of those worked. I also tried:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:71.0) Gecko/20100101 Firefox/71.0
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:71.0) Gecko/20100101 Firefox/71.0

but these didn't work either. I'm beginning to think something else is going on, but I don't have a clue what it could be. I just hope it keeps working in Basilisk cause I'd hate to have to use Firefox.

Is anybody else (on Windows or Linux) who uses Citibank experiencing this, or just me?

[pshipwrite]

ron_1, I am experiencing the same Citibank login problem on Windows 7 with PM 28.8.0. I searched the Pale Moon forums for Citi and found your posts here in the "Pale Moon for Linux" forum. I suspect Citi updated their website browser security checks around December 23rd. Like you, I have tried numerous UA overrides for citi.com but none have worked.

I am also using another browser as a workaround (Opera). I hope this issue can be resolved since PM is my primary browser.

[back2themoon]

I hope this issue can be resolved since PM is my primary browser.

Make sure to contact the bank...

[pshipwrite]

back2themoon, I have contacted Citibank in previous years when such "UA sniffing" problems occurred. However, Citi was not at all responsive. Their customer service representatives simply said I must use Google Chrome, Mozilla Firefox, Safari, or Internet Explorer (or Microsoft Edge if on Windows 10) - Citigroup does NOT support any other browser. I tried to reason with them that their browser security checks should be based on functionality not on browser self-identification but to no avail.

[back2themoon]

Well, in such a case, I'd rather switch bank than browser. I mean, they make tons of money and don't even bother to listen to their customers for a simple matter? I'm lucky enough to use two banks that both work fine with Pale Moon (as they should - they're not doing me any favours).

[pshipwrite]

I agree with you, back2themoon, I would switch to another bank if I could. However, given the unique financial relationship I have with Citi, that is not possible at this time.

[ron_1]

I'd like to know if it's not UA sniffing causing this, what is?

[pshipwrite]

Yes, I'm not sure the problem is solely UA sniffing. Having tried a gazillion UA overrides, reason and logic says something else may be going on.

[ron_1]

Is there anything in the Web Developer (under Tools menu option) that I can look at that might shed some light on this?

[Moonchild]

Citibank has been an on-going problematic site for us and they have no intention of being browser-agnostic or even being in any way reasonable to their clients when it comes to on-line banking.
Contacting them has proven less than useful -- if you are using them and want to use their on-line banking, please use one of their very short list of "approved" browsers. There really isn't much else to do about it as they will continue to target only those browsers and will continue to explicitly block other web clients when they can.

[ron_1]

Yeah, I know MC. Right now my big concern is that sooner or later it won't work in Basilisk either.

[Pallid Planetoid]

I hope this issue can be resolved since PM is my primary browser.

Make sure to contact the bank...

Citibank isn't going to care about supporting Pale Moon -- they are just going to say that PM isn't an acceptable browser and that will be the end of it.

[Pallid Planetoid]

I agree with you, back2themoon, I would switch to another bank if I could. However, given the unique financial relationship I have with Citi, that is not possible at this time.

First of all -- point of reference; this recent issue also occurs in Windows (in my case Win10).

Back to my reply to the suggestion of changing banks:

I'm not about to quit Citibank considering I've had an account with them since 1957 (over 60 years) and as such have a unique relationship including a special account that no one else can have that is both free and provides me with interest on my balance at the same time. Because of my long history with Citibank I've relegated myself to using my "Open with...." add-on to open the login page in another browser by just right-clicking on the login page in Pale Moon and selecting anyone of a number of alternate browsers that work with Citibank. This allows me to keep using Pale Moon for everything (which is my priority) and simply redirecting Citibank to an alternate browser to account for this new issue that has recently cropped up.

What I'm hoping is that at some point down-the-road whatever change has created this problem will be addressed (likely inadvertently) by Citibank since the issue may be unintended consequences of some change to their login page (which has occurred in the past i.e. weird log-off behavior was present for some time that eventually resolved itself).

That said, however -- I'm also wondering if the PM 28.8 update may be contributing to the problem instead of any Citibank modifications to their web-page.

This issue has started very close in proximity of time to the PM 28.8 update when thinking back to when this all started. And the issue persists in Safe-Mode and using a new clean profile for what that's worth.....

So if anyone is still using the prior release of PM and are using Citibank -- please post your results using the bank -- thanks in advance.

Question answered below...

[Pallid Planetoid]

.... I'm also wondering if the PM 28.8 update may be contributing to the problem instead of any Citibank modifications to their web-page.

This issue has started very close in proximity of time to the PM 28.8 update when thinking back to when this all started. And the issue persists in Safe-Mode and using a new clean profile for what that's worth.....

So if anyone is still using the prior release of PM and are using Citibank -- please post your results using the bank -- thanks in advance.

No need --- Refer to this post regarding same topic involving Windows viewtopic.php?f=3&t=23513&p=180719#p180719 that answers this question (same issue present in the prior Pale Moon release).

[Pallid Planetoid]

Is there anything in the Web Developer (under Tools menu option) that I can look at that might shed some light on this?

For what it's worth this is what I get for errors in the Web Console:

Code: Select all

Timestamp: 12/30/2019 6:06:58 PM
Error: ReferenceError: mboxCreate is not defined
Source File: https://online.citi.com/US/JPS/portal/Index.do?Promo_ID=SPBL
Line: 948
Timestamp: 12/30/2019 6:07:02 PM
Error: TypeError: document.getElementById(...) is null
Source File: chrome://butwhymod/content/browser.js
Line: 28
Timestamp: 12/30/2019 6:07:46 PM
Error: TypeError: document.getElementById(...) is null
Source File: chrome://butwhymod/content/browser.js
Line: 28

The first two errors are the result of rendering the log-in page and the third (last) error the result of attempting to login (which produces the error in question: "We're sorry. Citi.com is temporarily unavailable" etc etc....)

[Pallid Planetoid]

Yeah, I know MC. Right now my big concern is that sooner or later it won't work in Basilisk either.

Hmm, another perspective would be to approach the situation from the opposite direction --- that is to say (in full recognition that they are not the same browser just as most browsers are not the same in many respects); if the page works in a little known XUL browser like Basilisk then one could surmise there might be a way to make the same page work an another better known XUL browser like Pale Moon. (that is, from the perspective of a neophyte.... )