Private Browsing Tor Proxy not working anymore in Abrowser

5 risposte [Ultimo contenuto]
oysterboy

I am a member!

I am a translator!

Offline
Iscritto: 02/01/2011

On my main computer, the Private Browsing Tor Proxy addon is not working anymore in Abrowser. It does work in IceCat, and still works in Abrowser on my secondary computer. I may have changed some setting Abrowser (although I can't recall I did...). Can anyone help me fix that problem (I have no clue what to look for and search engines don't provide any information)?

oysterboy

I am a member!

I am a translator!

Offline
Iscritto: 02/01/2011

Cannot edit the first message, so here's some additional information: when I write that the addon doesn't work, what I mean is that when a Private Browsing opens, I don't see the Private Browsing Tor Proxy popup message notifying me that the Proxy has changed. A visit to http://check.torproject.org confirms that the Private session is not using tor.

oysterboy

I am a member!

I am a translator!

Offline
Iscritto: 02/01/2011

Follow-up: a brand new ~/.mozilla/abrowser profile fixes the problem, so I guess I have a setting somewhere that conflicts with the addon (now what could that be, I have no idea!). Maybe some modification in about:config?

cooloutac
Offline
Iscritto: 06/27/2015

have you made any changes, like in pizza's thread, or from supertramps pastebin? i had to dial back some changes myself that caused issues. I'm just sticking with pizza's recommendations now. I do think there is something that affects vpn in about:config, can't remember what it is. Only extra one besides the wiki tutorial examples i'm using now is the OCSP to true setting.

maybe media.peerconnection.enabled ?

oysterboy

I am a member!

I am a translator!

Offline
Iscritto: 02/01/2011

I thnk I made some changes at some point to try to get Firefox Hello to work (I didn't succeed by the way). Anyway, I started from a new profile and the problem is now solved!

oysterboy

I am a member!

I am a translator!

Offline
Iscritto: 02/01/2011

Broken again... Maybe by the latest abrowser updates?