Opened 2 weeks ago

Last modified 2 weeks ago

#33669 new defect

"Pluggable Transport process terminated" but Tor keeps on going (and of course doesn't work)

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ux-team anticensorship-wants
Cc: dcf, cohosh, phw, catalyst, ahf Actual Points:
Parent ID: #19001 Points:
Reviewer: Sponsor:


In I encountered the unfortunate situation where my snowflake client exited:

Feb 25 14:36:24.458 [warn] Pluggable Transport process terminated with status code 512

It still remains unclear whether snowflake had a bug that crashed it, or if Tor has a bug that made it close the socket to snowflake.

But either way, after this event Tor quietly cries to itself:

Feb 25 14:36:44.825 [warn] The connection to the SOCKS5 proxy server at just failed. Make sure that the proxy server is up and running.

and Tor Browser has no idea this is happening, or that trying to use Tor is now hopeless.

We should figure out something smarter that Tor should do in this situation. Perhaps it should exit, forcing the user to notice? Perhaps it should emit an event that Tor Browser picks up on? Maybe we have an even better idea?

Child Tickets

Change History (3)

comment:1 Changed 2 weeks ago by cohosh

Parent ID: #19001

comment:2 Changed 2 weeks ago by nickm

Cc: ahf added
Keywords: anticensorship-wants added
Milestone: Tor: 0.4.4.x-final

What version of Tor was this?

Adding ahf to the cc because I think he's worked on the "tor doesn't handle crashing pluggable transports right" problem before.

comment:3 in reply to:  2 Changed 2 weeks ago by arma

Replying to nickm:

What version of Tor was this?

I started with dcf's Tor Browser 9.5alpha5 variant from but then I swapped in my own Tor binary, built from my branch debug33336.

So, Tor based on adding commit 39f0c52a to commit c9bd3579.

Note: See TracTickets for help on using tickets.