Firefox cannot use shadowsocks but Safari or Chrome can use it in MacOS

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
3 years ago
3 years ago

People

(Reporter: mango1220, Unassigned, NeedInfo)

Tracking

41 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bugday-20151012])

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150929144111

Steps to reproduce:

I cannot use Firefox to visit websites by using shadowsocks in MacOS. However I can use Safari or Chrome to visit these websites successfully. I find that the setting about network in Firefox is set to using the proxy setting of system. I try to choose other options but I find it doesn't work. So I want to know what should I do, or is this a bug actually?

Updated

3 years ago
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86

Comment 1

3 years ago
Thanks for reporting. (In reply to mango1220 from comment #0)
> User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0)
> Gecko/20100101 Firefox/41.0
> Build ID: 20150929144111
> 
> Steps to reproduce:
> 
> I cannot use Firefox to visit websites by using shadowsocks in MacOS.
> However I can use Safari or Chrome to visit these websites successfully. I
> find that the setting about network in Firefox is set to using the proxy
> setting of system. I try to choose other options but I find it doesn't work.
> So I want to know what should I do, or is this a bug actually?


Thanks for reporting. 
Shadowsocks works through a self hosted Server, needs some tricky configuration to make a browser connect through another client. Configuring Server and Client requires config files. Have you done anything like that. It may need different settings for Firefox unlike Chrome and Safari. Please check with Shodowsocks to work with. Moreover it
Flags: needinfo?(mango1220)
Whiteboard: [bugday-20151012]

Comment 2

3 years ago
Base of lack of information from the reporter this bug will have the Status: Resolved as incomplete.
If you want to add more info that can help to understand this bug please reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.