after upgrade to the last version of torbrowser i encounted two trouble question.
first , how to combine COMMANDs to specify multiple options simultaneously with what form? (bridgegb-email)
second, i use fte bridge but tor failed to launch it at beginning.
even i changed the fte entry in the torrc-defaults file with absolute path insdead of relative path, still dont work. I also copyed dll files in the parent folder of PluggableTransports into itself, no effect.
Its prompt something like that Map can not find the specified file
log attached, thanks in any form of help.
Trac: Username: djgend
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
2017/2/26 5:28:35.500 [WARN] Failed to create child process G:\Program: ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£ 6 2017/2/26 5:28:35.500 [WARN] Managed proxy at 'G:\Program' failed at launch.
seem to be the important lines in the log. So, this worked with 6.0.8? Could you try a vanilla version (https://dist.torproject.org/torbrowser/6.0.8) to confirm this? Could you give steps to reproduce your problem (Where did you put Tor Browser? How did you start it? How did you configure it to use FTE? etc.).
Now problem is completely eliminated, even if leave relative notation in the torrc-default or torrc config file not changed it to absolute path notation, its works like a charm.
Trac: Username: djgend Status: needs_information to closed Resolution: N/Ato fixed
Hi, glad you got your fteproxy issue sorted out. Alas, this is a bug tracker helping us to coordinate our development. Usage questions are out of scope. We have plenty of other venues for this kind of issues, though, see: https://www.torproject.org/about/contact.html.en and pick your favorite one. Good luck!
Trac: Status: reopened to closed Resolution: N/Ato not a bug
UPDATED, i encountered this problem once again, and figured out that its not regarding about the path variable as mentioned above. Its simply need to change the line "TorBrowser\Tor\PluggableTransports\fteproxy" to "PluggableTransports\fteproxy" within torrc-defaults, then everything works like a charm. Nothing need to be entered to the cmd.
UPDATED, i encountered this problem once again, and figured out that its not regarding about the path variable as mentioned above. Its simply need to change the line "TorBrowser\Tor\PluggableTransports\fteproxy" to "PluggableTransports\fteproxy" within torrc-defaults, then everything works like a charm. Nothing need to be entered to the cmd.
Thanks. So, to understand this issue better: Is this a problem with our setup? I.e. does this happen with a freshly downloaded Tor Browser. Or is this a mistake you made with your bridge configuration?