I downloaded it two days ago. I applied for a credit card, and all went well until the final step when I SENT the application and all its data. I got a #020001 error code saying: "Ooops! Something went wrong at our end."
However, the application HAD gone through (as my email proved,) but the bank's response was not able to get through, so to speak, thus the error. Could this have something to do with permissions or other security settings blocking the particular sort of response they were trying to send? What say ye?
Thanks for any wisdom.
78.4.0esr: browser & my bank don't communicate well
- SteelyDon
- Posts: 324
- Joined: March 29th, 2004, 4:49 pm
- Location: Canada
- DanRaisch
- Moderator
- Posts: 127231
- Joined: September 23rd, 2004, 8:57 pm
- Location: Somewhere on the right coast
Re: 78.4.0esr: browser & my bank don't communicate well
You were working on a web site and got an error message. To what e-mail are referring?
- SteelyDon
- Posts: 324
- Joined: March 29th, 2004, 4:49 pm
- Location: Canada
Re: 78.4.0esr: browser & my bank don't communicate well
Sorry it's unclear. I was making application for a credit card. The error message indicated that there was an error regarding the message when I finally hit SEND. I tried again, same response. Later, when I checked email, I had mail from the bank saying that the application had been accepted (twice!!) so it seems that my application had indeed gone through but something prevented their system from advising my browser that it had worked, and instead I got the error message, instead of receiving something like "Thank you for your application, we'll be in touch."
Now, when I try to verify the account, I get the same #020001 error code saying: "Ooops! Something went wrong at our end." Something prevents the browser and their system from making that final communication when I submit info. I'm not very techie, but I wonder if it is permissions or settings not being adequate for whatever the protocol are for secure transmission, but I know only slightly more about these things than my dog does.
I should add that it's Windows 7 OS.
Now, when I try to verify the account, I get the same #020001 error code saying: "Ooops! Something went wrong at our end." Something prevents the browser and their system from making that final communication when I submit info. I'm not very techie, but I wonder if it is permissions or settings not being adequate for whatever the protocol are for secure transmission, but I know only slightly more about these things than my dog does.
I should add that it's Windows 7 OS.
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: 78.4.0esr: browser & my bank don't communicate well
And to be clear, this is in 78.4.0 & not in 38.0?
Are you using Private Browsing?
Extensions?
Have you set "higher" (built-in) blocking abilities, different from FF's defaults?
Are you using Private Browsing?
Extensions?
Have you set "higher" (built-in) blocking abilities, different from FF's defaults?
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
- SteelyDon
- Posts: 324
- Joined: March 29th, 2004, 4:49 pm
- Location: Canada
Re: 78.4.0esr: browser & my bank don't communicate well
'Average' settings. 78.4.0esr.
I think it perhaps really IS on their end. I downloaded VIvaldi, same response. I tried Edge on wife's W10 laptop, same thing.
Thanks for the replies.
I think it perhaps really IS on their end. I downloaded VIvaldi, same response. I tried Edge on wife's W10 laptop, same thing.
Thanks for the replies.
- DanRaisch
- Moderator
- Posts: 127231
- Joined: September 23rd, 2004, 8:57 pm
- Location: Somewhere on the right coast
Re: 78.4.0esr: browser & my bank don't communicate well
Well, that error message was sort of suggesting that it was on the provider's end from the start. Moving to MozillaZine Tech as the issue is effecting all tested browsers.