Getting logged out when click links inside an Etrade account
Windows 10 64 bit, Firefox 7.0.2 After I log into an Etrade account, if I click on any link (such as a stock symbol) within the account, I am returned to the Etrade login page. If I use the back button on the browser I am returned to the page I was on (I was not logged out). I never can get to the stock symbol or other link within Etrade. I have tried changing every add on or extension change (especially security settings), refreshing Firefox, running in safe mode and actually reinstalling Firefox without success. I think I have seen this on other websites also, but this type action does not happen on all websites. This does not happen when using Chrome.
Valgt løsning
The prefs are OK, so no need to take action. There can still be something weird going on if this happens on multiple websites.
You do not seem to have extensions installed apart from Avira Browser Safety that could be causing this.
Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.
- https://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
- https://www.7tutorials.com/4-ways-boot-safe-mode-windows-10
Alle svar (10)
Many site issues can be caused by corrupt cookies or cache.
Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.
- How to clear the Firefox cache {web link}
If there is still a problem, Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh). Did this help?
While you are in safe mode;
Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.
How to disable Hardware Acceleration {web link}
dphunter said
if I click on any link . . .
When I find a link I want to check out, I open it in a new tab/window. Then when I am done, I close it and am back where I started.
I'm afraid that was not the problem. Still get logged out when clicking just about any link within Etrade.
You aren't blocking the referrer as this can cause such issues?
You can check 'referer' prefs on the about:config page and make sure they are default and not user set (bold).
- network.http.*refer
You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.
Thanks - I'm not familiar with the default for these, but attached are my settings for the referer prefs. I'll be glad to try a change them if you see something askew.
Valgt løsning
The prefs are OK, so no need to take action. There can still be something weird going on if this happens on multiple websites.
You do not seem to have extensions installed apart from Avira Browser Safety that could be causing this.
Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.
Same result in safe mode. I am sure I was in safe mode - "safe mode" in the corners.
Also renamed the Prefs file - no change, problem still occurs.
GOT IT WORKING! I had done two things when it started working, so I don't know for sure which one was the solution - I think the latter. 1) I refreshed FF again, even though I had done this before. 2) at the same time, I deleted the autologin files for the websites I was having trouble with (there were two, Etrade was one), and turned the auto login function off. I manually typed in the login and PW information, then proceeded to the site. Bear in mind, I could reliably login before, but when I tried clicking on a link within the site, it logged me out. I turned the autologin function back on and it is working as expected. It also fixed the same problem I noticed on another site. So, it's hard to believe the login info from the autologin was corrupted somehow especially since it didn't keep me logging into the first page, but manually retyping it in seemed to fix the problem.
Thanks for your help.
That was very good work. Well Done. Please flag your last post as Solved Problem as this can help others with similar problems.