Recent mod_wsgi Issue with Self-Hosted Sync Server

Reuben Farrelly reuben-mozilla-sync-dev at
Wed Sep 3 21:25:54 PDT 2014

No joy, I'm afraid.  I uncommented those options in my syncserver.ini 
file and now server side I see this: - - [04/Sep/2014:13:29:57 +1000] "GET /token/1.0/sync/1.5 
HTTP/1.1" 401 109 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) 
Gecko/20100101 Firefox/32.0"

and this:

[Thu Sep 04 13:29:59.134875 2014] [wsgi:error] [pid 18941] 
FutureWarning: The BrowserID certificate format has not been finalized 
and may change in backwards-incompatible ways.  If you find that the 
latest version of this module cannot verify a valid BrowserID assertion, 
please contact the author.
[Thu Sep 04 13:29:59.134948 2014] [wsgi:error] [pid 18941] 
super(LocalVerifier, self).__init__(**kwargs)
[Thu Sep 04 13:29:59.153143 2014] [wsgi:error] [pid 18941] 
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS 
connection (1):
[Thu Sep 04 13:30:00.470899 2014] [wsgi:error] [pid 18941] 
0.001425027847290039, "code": 401, "request_time": 1.3324501514434814, 
"remoteAddressChain": [""], "agent": "Mozilla/5.0 (Windows 
NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0", 
"tokenserver.assertion.verify": 1.329387903213501, 
"token.assertion.verify_success": 1, "path": 
"", "method": "GET"}

Nothing progresses past that point and sync never kicks off - it 
successfully authenticates me but the actual sync process itself never 

I guess this points to something SSL related happening (or not) within 

Incidentally, I've noticed that every time I disconnect and reconnect my 
sync settings in Firefox it resets the services.sync.tokenServerURI 
setting back to default.  This is extremely annoying when testing or 
when sync breaks and I need to disconnect/reconnect the account - is 
this setting supposed to default back by design?


On 01/09/2014 4:13 PM, Ryan Kelly wrote:
> I'm not familiar enough with mod_wsgi to guess at the cause here, but I
> note that it's erroringout while trying to make an SSL connection to our
> hosted browserid verifier.
> You may be able to work around the issue by enabling the local verified.
>   In your syncserver.ini there should be a commented-out section with the
> phrase "LocalVerifier" - try enabling that and see if it helps.
>    Cheers,
>      Ryan
> On 30/08/2014 8:53 PM, Reuben Farrelly wrote:
>> Hi,
>> I've recently noticed that my sync server appears to be broken, and have
>> determined that the cause of this was an upgrade to the latest mod_wsgi.
>> I'm using apache-2.4.10 with mod_wsgi and Python-2.7.8 on Gentoo Linux.
>> I've tested downgrading mod_wsgi to 3.5 and things appear to work OK.
>> But with mod_wsgi 4.2.7 sync fails, with this logged on the server side
>> in the apache error logs:
>> [Sat Aug 30 20:20:57.926151 2014] [wsgi:error] [pid 29354]
>> INFO:requests.packages.urllib3.connectionpool:Resetting dropped
>> connection:
>> [Sat Aug 30 20:20:57.927108 2014] [wsgi:error] [pid 29354]
>> ERROR:mozsvc:Uncaught exception while processing request:
>> [Sat Aug 30 20:20:57.927161 2014] [wsgi:error] [pid 29354] GET
>> [Sat Aug 30 20:20:57.927171 2014] [wsgi:error] [pid 29354] Uncaught
>> exception:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: reuben-mozilla-sync-dev.vcf
Type: text/x-vcard
Size: 4 bytes
Desc: not available
URL: <>

More information about the Sync-dev mailing list