I've been getting an error message about Gmail detecting a slow connection...
This started happening a couple days ago. When logging in to Gmail, there's a pause and the error message about a slow connection.
It seems to have started when Firefox was updated to v32.0
Wybrane rozwiązanie
Do you connect to the web directly or through a proxy (a proxy could be a filter provided by your security software, or a VPN service, etc.)? You could experiment with your connection setting here:
"3-bar" menu button (or Tools menu) > Options > Advanced > Network mini-tab > "Settings" button
The default is "Use system proxy settings" which should use the settings in Windows/IE for your LAN connection. You also can try "No proxy" to see whether that helps.
And... the usual suggestions:
When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
Alternately, you also can clear Firefox's cache completely using:
"3-bar" menu button (or Tools menu) > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now"
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site:
- right-click and choose View Page Info > Security > "View Cookies"
- (menu bar) Tools > Page Info > Security > "View Cookies"
Then try reloading the page. Does that help?
To rule out extensions as a possible culprit, could you try the site in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions, some advanced features, and some custom settings. More info: Diagnose Firefox issues using Troubleshoot Mode.
You can restart Firefox in Safe Mode using either
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- (menu bar) Help menu > Restart with Add-ons Disabled
Note: Flash and other plugins still run
After Firefox closes, a small dialog should appear: click "Start in Safe Mode" (not Reset)
Any difference?
Przeczytaj tę odpowiedź w całym kontekście 👍 1Wszystkie odpowiedzi (2)
Wybrane rozwiązanie
Do you connect to the web directly or through a proxy (a proxy could be a filter provided by your security software, or a VPN service, etc.)? You could experiment with your connection setting here:
"3-bar" menu button (or Tools menu) > Options > Advanced > Network mini-tab > "Settings" button
The default is "Use system proxy settings" which should use the settings in Windows/IE for your LAN connection. You also can try "No proxy" to see whether that helps.
And... the usual suggestions:
When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
Alternately, you also can clear Firefox's cache completely using:
"3-bar" menu button (or Tools menu) > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now"
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site:
- right-click and choose View Page Info > Security > "View Cookies"
- (menu bar) Tools > Page Info > Security > "View Cookies"
Then try reloading the page. Does that help?
To rule out extensions as a possible culprit, could you try the site in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions, some advanced features, and some custom settings. More info: Diagnose Firefox issues using Troubleshoot Mode.
You can restart Firefox in Safe Mode using either
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- (menu bar) Help menu > Restart with Add-ons Disabled
Note: Flash and other plugins still run
After Firefox closes, a small dialog should appear: click "Start in Safe Mode" (not Reset)
Any difference?
Thanks, JScherr2000, your first idea worked. My son just admitted that he was "trying something" with the 'no proxy' setting and forgot to change it back.