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

iceweasel keeps connecting but receives nothing

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by ruud_144

more options

using the jessie debian distribution, I today upgraded iceweasel from 31.8.0-1~deb8u1 to 38.4.0-1~deb8u1 on an amd64 platform. The old version was having no single problem, but the new version keeps saying 'connecting to accountname' withhout receiving anything.

I have no clue where I should start. I did not change my account settings in any way. Has iceweasel got new settings that have to be set that I am not aware of?

Also am I having a bit of trouble finding the debian package to reinstall the old version. Where can I find it?

thanks in advance, ruud

using the jessie debian distribution, I today upgraded iceweasel from 31.8.0-1~deb8u1 to 38.4.0-1~deb8u1 on an amd64 platform. The old version was having no single problem, but the new version keeps saying 'connecting to accountname' withhout receiving anything. I have no clue where I should start. I did not change my account settings in any way. Has iceweasel got new settings that have to be set that I am not aware of? Also am I having a bit of trouble finding the debian package to reinstall the old version. Where can I find it? thanks in advance, ruud

Modified by ruud_144

Chosen solution

Found it. My company made a network change so that it was not necessary any more to use the proxy. The proxy was still used in the configuration. The old version was apparently having no issues with that. This new version obviously did.

Configuring 'no proxy' did the trick.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

Found it. My company made a network change so that it was not necessary any more to use the proxy. The proxy was still used in the configuration. The old version was apparently having no issues with that. This new version obviously did.

Configuring 'no proxy' did the trick.