On 2022-11-23 22:15, Ali Farzanrad wrote:
Hi,
I'm living in Islamic Dictatorship of Iran and here I can use bridges
provided by this Telegram bot: @GetBridgesBot
Also you might get bridges from https://bridges.torproject.org
Also you can purchase a VPS from any hosting like 1984.is and run your
own obfs4 bridge there.
I'm not sure about your question (why? who? how?) but I hope give you
good alternatives.
u...@disroot.org wrote:
When I click on "Configure Connection/Select a
Built-In Bridge", no bridges are displayed in the
popup. In my circumstances where I have to use a
bridge, this makes Tor Browser practically
useless. For tons of other people living in
repressive regimes this is true as well. Now I
either need to use Gmail or obtain a RiseUp
invite code somewhere, because Tor arbitrarily
decided to require one of these two email
providers for obtaining bridges by email.
Remember, Google is an ad company. Anyway, why?
Who? How? That's the questions I'm here for.
Thank you! Previously, Tor website was blocked by my provider, but seems
like this is not the case anymore. However, the problem is not solved: I
still cannot use Tor Browser even with the new bridges from the Tor
Browser's website. Here are the logs from Tor Browser:
11/23/22, 19:49:51.933 [NOTICE] DisableNetwork is set. Tor will not make
or accept non-control network connections. Shutting down all existing
connections.
11/23/22, 19:51:49.894 [NOTICE] New control connection opened from
127.0.0.1.
11/23/22, 19:52:03.920 [NOTICE] DisableNetwork is set. Tor will not make
or accept non-control network connections. Shutting down all existing
connections.
11/23/22, 19:52:03.921 [NOTICE] Switching to guard context "bridges"
(was using "default")
11/23/22, 19:52:17.285 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/23/22, 19:52:17.285 [NOTICE] Opened Socks listener connection (ready)
on 127.0.0.1:9150
11/23/22, 19:52:18.690 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:52:18.700 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:52:19.890 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:52:19.900 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:52:47.436 [NOTICE] Closing no-longer-configured Socks
listener on 127.0.0.1:9150
11/23/22, 19:52:47.438 [NOTICE] DisableNetwork is set. Tor will not make
or accept non-control network connections. Shutting down all existing
connections.
11/23/22, 19:53:46.835 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/23/22, 19:53:46.836 [NOTICE] Opened Socks listener connection (ready)
on 127.0.0.1:9150
11/23/22, 19:53:47.141 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:53:47.142 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:53:48.161 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:53:48.162 [WARN] Can't use bridge at [scrubbed]: there is
no configured transport called "obfs4".
11/23/22, 19:54:21.184 [NOTICE] New control connection opened from
127.0.0.1.
