This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How come version 3.6.3 will not allow me to access my online banking while version 3.6.2 can when they are both exactly the same setup?

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 4 views
  • Last reply by cor-el

I have two computers. Both had Fire Fox 3.6.2. I then upgraded one to 3.6.3. I then tried to access my online banking and I was unable to with the Version 3.6.3. I then went to my other computer and I had no problems accessing it with the one that has 3.6.2. On the computer with 3.6.2 that was upgraded i did not change anything. It has the same add-on, settings, etc. This happens to some other sites as well. I have read and looked through all the help files and nothing helped. I've done everything except uninstall Fire Fox and reinstall 3.6.2 (if i can find it) to see if that will work. I really don't want to do that but if i must then i shall.

This happened

Every time Firefox opened

== I upgraded my fire fox from version 3.6.2

I have two computers. Both had Fire Fox 3.6.2. I then upgraded one to 3.6.3. I then tried to access my online banking and I was unable to with the Version 3.6.3. I then went to my other computer and I had no problems accessing it with the one that has 3.6.2. On the computer with 3.6.2 that was upgraded i did not change anything. It has the same add-on, settings, etc. This happens to some other sites as well. I have read and looked through all the help files and nothing helped. I've done everything except uninstall Fire Fox and reinstall 3.6.2 (if i can find it) to see if that will work. I really don't want to do that but if i must then i shall. == This happened == Every time Firefox opened == I upgraded my fire fox from version 3.6.2

All Replies (3)

Your plugins list shows outdated plugin(s) with known security and stability risks.

# Shockwave Flash 10.0 r32
# Next Generation Java Plug-in 1.6.0_19 for Mozilla browsers 

Update the Java and Flash plugin to the latest version. See http://java.sun.com/javase/downloads/index.jsp#jdk (you need JRE) http://www.adobe.com/software/flash/about/ --- "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now" "Remove the Cookies" from sites that cause problems: Tools > Options > Privacy > Cookies: "Show Cookies"

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes). See Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems and Troubleshoot issues with plugins like Flash or Java to fix common Firefox problems

I have done all that you have told me and it still doesn't allow me access to said site.

Again, my other computer is EXACTLY the same setup except the version is 3.6.2!

That being the older java/flash/ etc (I even updated the Java/Flash/etc. without updating to Fire Fox Version 3.6.3 and it still lets me access said site)! That includes ADD-ONS, bookmarks, etc.!

The version 3.6.2 has ZERO problems logging onto the site! IT IS VERSION 3.6.3 that has 100% problems logging on, EVEN IS SAFE MODE with everything turned off (add-ons and what not)!

Does ANYONE KNOW how I can UNINSTALL Fire Fox 3.6.3 and install ONLY Fire Fox 3.6.2 because I am sure that is the problem!

Hello,

I have exact the same problem. When I have run through the login pages of my onlinebanking the final site were I can perform the banking operations is shown in a complete mess as a text only page. In addition the logout link does not work and I get a safety message when trying to access the next time.

This problem also just appeared after the update from 3.6.2 to 3.6.3.