Random 'Unable to find the proxy server' back again, but rarer

UNCONFIRMED
Unassigned

Status

()

P3
normal
UNCONFIRMED
3 years ago
a year ago

People

(Reporter: raysatiro, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog][proxy])

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150525030205

Steps to reproduce:

Normal web surfing. I click to open a link in a tab or type something in to the search box.

Manual proxy configuration,
localhost 8888 for all protocols
No proxy for localhost, 127.0.0.1

This is too rare I'm not going to be able to get a regression window. The last time I saw it was a week ago.


Actual results:

Unable to find the proxy server

I am using the web debugging proxy Fiddler v4.5.1.0 and I can see nothing in its activity to indicate a connection when this happens. 

Also see bug #1101776 and bug #1123324. Gijs said open a new bug.



Expected results:

.
(Reporter)

Updated

3 years ago
Component: Untriaged → Networking
OS: Unspecified → Windows 7
Product: Firefox → Core
Hardware: Unspecified → x86_64
Version: 41 Branch → Trunk
https://bugzilla.mozilla.org/show_bug.cgi?id=1123324#c81

It has never happened before 12.5. and it happened couple of times after 12.5?

It is probably problem with DNS resolution. After looking a bit into change set  there is my patch that prevents retry to connect if we are offline.
Can it be that network went offline for short time?

What is the value of preference disableIPv6?
(Reporter)

Comment 2

3 years ago
(In reply to Dragana Damjanovic [:dragana] from comment #1)
> https://bugzilla.mozilla.org/show_bug.cgi?id=1123324#c81
> 
> It has never happened before 12.5. and it happened couple of times after
> 12.5?

If you are referring to the date, then yes. 20150510030207 as far as I know was fine. I use Nightly regularly so I can assert prior builds were fine as well. This is an rare issue so it's possible it was in builds before 20150512030215 but only after my upgrade did I first encounter it again. 

> It is probably problem with DNS resolution. After looking a bit into change
> set  there is my patch that prevents retry to connect if we are offline.
> Can it be that network went offline for short time?

Nope the network is not offline. I've seen it twice today, actually. I can just click try again and the page will load. It's sporadic and rare. I don't know why I've seen it twice today, that's a lot. I do have a lot of tabs open at the moment, all e10s.

I checked in Fiddler and went through the log (in addition to the live activity which I usually check) because sometimes Firefox will connect but not make a request and the log will say something like:
<timestamp> No HTTP request was received from Firefox new client socket, port 123.
But in these cases there aren't entries that match around the time I see the Unable to connect to proxy message. So I'm pretty sure Firefox isn't making the connection at all. I can't Wireshark localhost so I can't say for certain.

> What is the value of preference disableIPv6?

network.dns.disableIPv6 = false
(Reporter)

Comment 3

3 years ago
Just saw it again.

Version 	41.0a1
Build ID 	20150613030206
(Reporter)

Comment 4

3 years ago
Just saw this again. I'm using build ec77f5c19262 20150811011940 42.0a1
(Reporter)

Comment 5

3 years ago
Saw it again

Version 	43.0a1
Build ID 	20150909030223
(Reporter)

Comment 6

3 years ago
I've seen it about a dozen times since this morning.

Version 	43.0a1
Build ID 	20150921030204
Whiteboard: [necko-backlog]
(Reporter)

Comment 7

2 years ago
Just saw it, this time in Aurora. Proxy is set to localhost 8888.

Version 	52.0a2
Build ID 	20170118004007

Updated

2 years ago
Whiteboard: [necko-backlog] → [necko-backlog][proxy]
You need to log in before you can comment on or make changes to this bug.