Tor process killed when using bridges with pluggable transports

[QuMix64]

Hello, OnionFruit can't connect to Tor through Bridges, it says "Tor Process killed" (Killswitch enabled). I can't use direct connection because Tor is blocked in my country. Release version on dragonfruit.network doesn't have this issue, but there's no WebTunnel bridge I need. I'd be very grateful if you respond to it

[aspriddell]

The tor process OnionFruit is starting is being killed either due to a bad config or some other program interference.

If you're using webtunnel make sure you are adding bridge lines and they're showing up in the settings as well, I'm aware that selecting it then connecting without providing any lines will cause this issue to occur.

If you are able to, obfs4, snowflake and meek all come pre-configured and don't need additional lines provided to use

[QuMix64]

Thank you for the response! Of course, I use only proven bridges that work perfectly in the Tor browser and on the phone. As I said earlier, in the release version of OnionFruit, my obfs4 bridge works But I can't use this version because it doesn't support webtunnel

I can put the same bridge in a new version, but it doesn't work anymore

[aspriddell]

Can you upload logs? They're in the same place as the other version but it's called runtime.log and there's only one (see the GitHub wiki for the location and how to find them)

It's very likely there's a misconfiguration going on

[QuMix64]

runtime.log

[aspriddell]

Thanks for that, the issue isn't on your end, it's caused when .NET builds the app and it flattens a series of folders that causes some of the files to be moved and tor crashes as a result.

I'll take a look at getting that sorted and will update here when it's resolved

[QuMix64]

Thank you for your answers, I will be waiting for a new version!

[aspriddell]

The flattened directories were to blame; I have changed how the config file is written so it will now correctly work out the location of the plugins.

Please launch the program, allow it to update and restart and it should work now (updates may take around 30s to complete after closing the app).

Feel free to reopen if it hasn't fixed the issue.

[Zig-Rust-Odin]

@aspriddell hello Version 2024.1107.0 does not work with bridges Issue not yet resolved https://github.com/scriptzteam/Tor-Bridges-Collector

plain 

79.238.157.240:443 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677

[aspriddell]

The bridge you've quoted is not working most likely because it's not active anymore. If you are going to report issues with bridges please make sure you are using ones from the BridgeDB and not some archive of potentially outdated ones.

Additionally, this issue is for bridges that use pluggable transports (everything except for plain ones). I have updated the title to make this clearer but if you have any further problems please create a new issue.

[Zig-Rust-Odin]

79.238.157.240:443 It's the vanilla bridges that tor officially gave me.

Tor-Bridges-Collector In the android app InviZible pro basically works fine!

[aspriddell]

I had written my previous response in a way to make it generic for others looking for the issue, but was actually directly aimed at the bridge you had used:

2024-11-08 17:01:32.204 +00:00 [DBG] [tor]: Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Unexpected identity in router certificate; IDENTITY; count 1; recommendation warn; host 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677 at 79.238.157.240:443)
2024-11-08 17:01:33.173 +00:00 [DBG] [tor]: Tried connecting to router at 79.238.157.240:443 ID=<none> RSA_ID=1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677, but RSA + ed25519 identity keys were not as expected: wanted 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677 + no ed25519 key but got 3945339D491320FFEA43E646E3C4A26FE5DE8EFF + g2GcIP+XkjFAj+P5HKMtxX1tOc0Q09Z72xjgol+Omg8.
2024-11-08 17:01:33.174 +00:00 [DBG] [tor]: Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Unexpected identity in router certificate; IDENTITY; count 2; recommendation warn; host 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677 at 79.238.157.240:443)
2024-11-08 17:01:33.174 +00:00 [DBG] [tor]: 1 connections have failed:
2024-11-08 17:01:33.174 +00:00 [DBG] [tor]:  1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
2024-11-08 17:01:34.183 +00:00 [DBG] [tor]: Tried connecting to router at 79.238.157.240:443 ID=<none> RSA_ID=1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677, but RSA + ed25519 identity keys were not as expected: wanted 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677 + no ed25519 key but got 3945339D491320FFEA43E646E3C4A26FE5DE8EFF + g2GcIP+XkjFAj+P5HKMtxX1tOc0Q09Z72xjgol+Omg8.
2024-11-08 17:01:34.183 +00:00 [DBG] [tor]: Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Unexpected identity in router certificate; IDENTITY; count 3; recommendation warn; host 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677 at 79.238.157.240:443)

it says there was an issue connecting to the bridge, OnionFruit configured the bridge correctly as you can see below:

UseBridges 1
ClientTransportPlugin meek_lite,obfs2,obfs3,obfs4,scramblesuit,webtunnel exec .\lyrebird.exe
ClientTransportPlugin snowflake exec .\snowflake-client.exe
ClientTransportPlugin conjure exec .\conjure-client.exe -registerURL https://registration.refraction.network/api
Bridge 79.238.157.240:443 1714FC03DE40EAD9EDF20A10CAACDF6B6DFCF677

Either try a different transport that doesn't need configuring, or get some more bridges from BridgeDB - the servers are run by people who are free to turn them off whenever which might be what you're experiencing.

---

Edit: I have just tried with a fresh set of bridges from BridgeDB and have no issue using them, I would strongly recommend getting some more bridges and using them to see if that fixes your issue.

[Zig-Rust-Odin]

Is there a way to check if the bridge is working properly. Strange, I pinged it in cmd and it responded.

[aspriddell]

You just have to try them, if the connection doesn't work then get some more and keep trying until they work. Pinging the server and getting a response will tell you the server is reachable, but doesn't always mean it's acting as a bridge (i.e. tor is installed and running on it)