Anti-censorship issueshttps://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues2023-11-16T11:34:58Zhttps://gitlab.torproject.org/tpo/anti-censorship/gettor-project/OnionSproutsBot/-/issues/57TB for MacOS obtained from the gettor_bot (Telegram) did not work2023-11-16T11:34:58ZninaTB for MacOS obtained from the gettor_bot (Telegram) did not workOS: MacOS
Problem:
Two users reported they downloaded TB for MacOS from @gettor_bot on Telegram and got an error message (The application cannot be open) while trying to install it.
When they downloaded TB from our website (to be preci...OS: MacOS
Problem:
Two users reported they downloaded TB for MacOS from @gettor_bot on Telegram and got an error message (The application cannot be open) while trying to install it.
When they downloaded TB from our website (to be precise - from the mirror) - the installation competed without errors.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40306Log scrubber fails to scrub messages with multiple space-separated IP addresses2024-01-08T15:04:55ZCecylia BocovichLog scrubber fails to scrub messages with multiple space-separated IP addressesI noticed this while looking at the conjure server logs. The following diff introduces a failing unit test for this case:
```diff
diff --git a/common/safelog/log_test.go b/common/safelog/log_test.go
index b6a719e..267538c 100644
--- a/co...I noticed this while looking at the conjure server logs. The following diff introduces a failing unit test for this case:
```diff
diff --git a/common/safelog/log_test.go b/common/safelog/log_test.go
index b6a719e..267538c 100644
--- a/common/safelog/log_test.go
+++ b/common/safelog/log_test.go
@@ -107,6 +107,11 @@ func TestLogScrubberMessages(t *testing.T) {
"error dialing relay: wss://snowflake.torproject.net/?client_ip=1%3A2%3A3%3A%3Ad%3Ae%3Af = dial tcp xxx",
"error dialing relay: wss://snowflake.torproject.net/?client_ip=[scrubbed] = dial tcp xxx\n",
},
+ {
+ // multiple space-separated IP addresses
+ "Allowed stations: [10.0.1.1 10.0.1.2 10.0.1.3 10.0.1.4]\n",
+ "Allowed stations: [[scrubbed] [scrubbed] [scrubbed] [scrubbed]]\n",
+ },
} {
var buff bytes.Buffer
log.SetFlags(0) //remove all extra log output for test comparisons
```https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/39Add 10.0.1.7 to allowed ips at conjure server2023-11-08T16:12:14ZCecylia BocovichAdd 10.0.1.7 to allowed ips at conjure serverThere has been a new wireguard peer at `10.0.1.7`. Looking at the timestamp on `/etc/wireguard/wg0.conf`, it looks like it was added on September 25th.There has been a new wireguard peer at `10.0.1.7`. Looking at the timestamp on `/etc/wireguard/wg0.conf`, it looks like it was added on September 25th.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/179update "Get Bridges" instruction on the email we send out with GetTor email r...2023-11-07T16:52:51Zebanamebanam@torproject.orgupdate "Get Bridges" instruction on the email we send out with GetTor email requestsCurrent version:
> Step 3: Get Bridges (Optional)
If you believe that Tor is blocked where you are, you can use bridges to connect
to Tor. Bridges are hidden Tor relays that can circumvent censorship.
Tor Browser...Current version:
> Step 3: Get Bridges (Optional)
If you believe that Tor is blocked where you are, you can use bridges to connect
to Tor. Bridges are hidden Tor relays that can circumvent censorship.
Tor Browser includes a list of built-in bridges, which you should try first.
You can activate built-in bridges inside of Tor Browser's settings, under the
"Tor" menu. If built-in bridges don't work, try requesting different bridges,
which you can also do in the "Tor" menu inside Tor Browser's settings.
Update:
You can activate built-in bridges inside of Tor Browser's settings, under the
"Connection" menu. If built-in bridges don't work, try requesting different bridges,
which you can also do in the "Connection" menu inside Tor Browser's settings.
(thanks to @nina for noticing this!)https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/87unify volunteer instructions from support entry onto snowflake website2024-02-27T13:16:49ZRoger Dingledineunify volunteer instructions from support entry onto snowflake websiteWe have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension ...We have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension or the standalone proxy.
Rather than trying to keep both sets of instructions in sync, I think we should put the instructions on the snowflake.torproject.org page, and point to them from a much slimmer support entry.
To achieve this goal, there are currently two things that the support entry says that the snowflake.torproject.org website does not:
* You need to enable WebRTC in your browser, to usefully run the extension or to usefully load the embed. (If we could reliably have the extension or the embed page report that your WebRTC is missing and you need to fix that, then we could get away with not saying it on the webpage. So, feel free to do that instead if it is easier, but I am suspecting it is not easier. :)
* "Due to censorship of VPN servers in some countries, we kindly ask you to not run a snowflake proxy while connected to a VPN" as advised by @cohosh at https://forum.torproject.org/t/running-a-snowflake-proxy-behind-a-vpn-consequences-for-tor-users/2047/4 and then recorded by gus at https://gitlab.torproject.org/tpo/web/support/-/issues/296. Feel free also to change your mind about the "not on a VPN please" advice.
Once we have these two items either make their way onto the snowflake.torproject.org proxy instructions or have you tell us you don't intend to, then we should be all ready to remove the (redundant, already not as correct) text from the support entry.
Thanks!https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/38Update Lox Distributor Config file to request Lox type2023-11-09T03:49:09ZonyinyangUpdate Lox Distributor Config file to request Lox typeThis should work in tandem with an update to `rdsys` that partitions bridges in to a `lox` type. This will only require an update to the test config file in the lox-distributor repo but this issue is mostly a reminder to update once a `l...This should work in tandem with an update to `rdsys` that partitions bridges in to a `lox` type. This will only require an update to the test config file in the lox-distributor repo but this issue is mostly a reminder to update once a `lox` type exists.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/37Publish Lox crates on crates.io2023-11-23T18:05:31ZonyinyangPublish Lox crates on crates.ioPrior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to ...Prior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to `crates.io` [here](https://doc.rust-lang.org/cargo/reference/publishing.html)
Once the crates are created, we should update our pipeline to automatically push updates to the documentation as appropriate.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40305Upgrade tor on snowflake bridges to 0.4.8.8 for TROVE 2023 0042023-11-07T00:11:57ZDavid Fifielddcf@torproject.orgUpgrade tor on snowflake bridges to 0.4.8.8 for TROVE 2023 004https://lists.torproject.org/pipermail/tor-relays/2023-November/021373.html
> Today (2023-11-03) the Network Team has released [new Tor versions 0.4.7.16 and 0.4.8.8](https://forum.torproject.org/t/security-release-0-4-7-16-and-0-4-8-8/...https://lists.torproject.org/pipermail/tor-relays/2023-November/021373.html
> Today (2023-11-03) the Network Team has released [new Tor versions 0.4.7.16 and 0.4.8.8](https://forum.torproject.org/t/security-release-0-4-7-16-and-0-4-8-8/10064). These updates contains a fix to a remote crash bug (TROVE 2023 004). It is highly recommended that all relay operators upgrade to the new versions as soon as possible to maintain the network stability and security.
>
> For those running their Tor relay using the Tor Debian repository, expect the new deb package to be available soon.
>
> The patches prevents the issue from causing a crash in Tor. However, it will make Tor more noisy when the bug is triggered, including logging information about the remote peer that is the source or destination of the circuit in the path. Such information is important for our developers to diagnose the specific invariant within Tor's TLS logic that does not hold.
- [x] snowflake-01
- [x] snowflake-02
/cc @linusDavid Fifielddcf@torproject.orgDavid Fifielddcf@torproject.org2023-11-06https://gitlab.torproject.org/tpo/anti-censorship/gettor-project/OnionSproutsBot/-/issues/55@gettor_bot on Telegram does not work2023-11-06T12:01:00Znina@gettor_bot on Telegram does not workIt does not react to the commands.
Reported by two users and confirmed by meIt does not react to the commands.
Reported by two users and confirmed by memeskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/36Some bridgelines are not found in db after being added2024-01-17T17:15:58ZonyinyangSome bridgelines are not found in db after being addedThere seems to be a bug in the `lox-distributor` that occurs on the first sync with rdsys after a new Lox context is established. Several test bridge fingerprints are listed as `not found in Lox's Bridgetable. Save it as a new resource f...There seems to be a bug in the `lox-distributor` that occurs on the first sync with rdsys after a new Lox context is established. Several test bridge fingerprints are listed as `not found in Lox's Bridgetable. Save it as a new resource for now!' but this only happens for new databases and only on the first sync. It may not be a problem but should be looked into before Lox is ready for prod.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/35Create a telegram distributor for open invitations with rate limiting through...2024-01-08T15:49:44ZonyinyangCreate a telegram distributor for open invitations with rate limiting through the age of accountsFrom the [Lox Roadmap](https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/wikis/Lox-Roadmap) we want a telegram bot that can be used to request Lox open invitations.From the [Lox Roadmap](https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/wikis/Lox-Roadmap) we want a telegram bot that can be used to request Lox open invitations.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40039Add ShadowSocks plugable transport2023-11-02T08:07:01ZcypherpunksAdd ShadowSocks plugable transportIt is stronger crypto, has PFS and combat-proven in China. See
https://mullvad.net/en/help/intro-shadowsocks/
https://github.com/shadowsocks/shadowsocks-rust
I have succesfully done my experiment and speed is better than meek.
Tor --S...It is stronger crypto, has PFS and combat-proven in China. See
https://mullvad.net/en/help/intro-shadowsocks/
https://github.com/shadowsocks/shadowsocks-rust
I have succesfully done my experiment and speed is better than meek.
Tor --SOCKS--> SS local --/censor/--> SS server --> internethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/86snowflake on local network2023-11-01T10:30:11Zcypherpunkssnowflake on local networkI don't know much about network so please help me on that.
I am running a web server on iOS, and I tried to put iframe embedding on my web server's html page.
It's only on the local network, which means I can access the webpage through...I don't know much about network so please help me on that.
I am running a web server on iOS, and I tried to put iframe embedding on my web server's html page.
It's only on the local network, which means I can access the webpage through same Wi-Fi, will the snowflake effective on that case?
and I find snowflake is very slow, may I ask how many deployed server can bring the snowflake to the speed of regular website browsing, I hope I can help with that.
Thanks!https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40302Proxy hourly stats did not actually happen during that hour2023-10-30T16:44:18ZRoger DingledineProxy hourly stats did not actually happen during that hourMy snowflake proxy today said in its logs:
```
2023/10/27 09:53:58 In the last 1h0m0s, there were 53 connections. Traffic Relayed ↓ 999064 KB, ↑ 167798 KB.
2023/10/27 10:53:58 In the last 1h0m0s, there were 67 connections. Traffic Relaye...My snowflake proxy today said in its logs:
```
2023/10/27 09:53:58 In the last 1h0m0s, there were 53 connections. Traffic Relayed ↓ 999064 KB, ↑ 167798 KB.
2023/10/27 10:53:58 In the last 1h0m0s, there were 67 connections. Traffic Relayed ↓ 561833 KB, ↑ 97282 KB.
2023/10/27 11:53:58 In the last 1h0m0s, there were 63 connections. Traffic Relayed ↓ 124717270 KB, ↑ 6237157 KB.
2023/10/27 12:53:58 In the last 1h0m0s, there were 48 connections. Traffic Relayed ↓ 745608 KB, ↑ 97699 KB.
```
That "125 gigabytes" entry translates to... almost 35 megabytes per second of traffic, on average during the hour? Probably by only a few or even one user? This did not happen during that hour.
Looking at proxy/lib/pt_event_logger.go:
```
case event.EventOnProxyConnectionOver:
e := e.(event.EventOnProxyConnectionOver)
p.inboundSum += e.InboundTraffic
p.outboundSum += e.OutboundTraffic
p.connectionCount += 1
```
I.e. what is happening here is that the stats for the entire connection are counted during the hour that it closed.
See the forum for somebody else reporting this same issue (forum post noticed courtesy MarkC on irc): https://forum.torproject.org/t/impossible-metric-for-snowflake-proxy/9941/1
We should either (a) make the hourly "In the last 1h0m0s," be accurate, in the sense that they actually tell me what happened in the last 1h0m0s, or (b) change the log message so it's clearer it is telling me how many connections finished during that hour along with total transfer on those recently-closed connections.
I'd prefer solution 'a', since it is what I thought I was getting out of these log entries, and I was using it to e.g. try to judge what timezones my snowflake is popular.https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/34New Firefox CSP blocks WebAssembly.instantiate()2024-01-26T16:57:55ZCecylia BocovichNew Firefox CSP blocks WebAssembly.instantiate()After rebasing the lox client integration with Tor Browser (https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/116), I got a new error when trying to run the lox client code from the Preferences menu:
```
eval() and eval-lik...After rebasing the lox client integration with Tor Browser (https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/116), I got a new error when trying to run the lox client code from the Preferences menu:
```
eval() and eval-like uses are not allowed in the Parent Process or in System Contexts (Blocked usage in “chrome://browser/content/torpreferences/lox/lox_wasm.js”)
`WebAssembly.instantiateStreaming` failed because your server does not serve wasm with `application/wasm` MIME type. Falling back to `WebAssembly.instantiate` which is slower. Original error:
CompileError: call to WebAssembly.instantiateStreaming() blocked by CSP
load chrome://browser/content/torpreferences/lox/lox_wasm.js:154
init chrome://browser/content/torpreferences/lox/lox_wasm.js:312
eval() and eval-like uses are not allowed in the Parent Process or in System Contexts (Blocked usage in “chrome://browser/content/torpreferences/lox/lox_wasm.js”)
Could not request a lox open invitation CompileError: call to WebAssembly.instantiate() blocked by CSP
load chrome://browser/content/torpreferences/lox/lox_wasm.js:167
requestOpenInvite chrome://browser/content/torpreferences/lox/lox.js:36
```
The current branch I'm working on: https://gitlab.torproject.org/cohosh/tor-browser/-/commits/lox-115.4.0esr-13.5-1Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40301Non-fronted connections to the broker no longer work since 9fdfb3d1b53e911342...2023-10-30T16:27:44ZCecylia BocovichNon-fronted connections to the broker no longer work since 9fdfb3d1b53e9113422a7a2816b2a9af4450b4acThe changes in !182 caused a regression for client configurations that only provide a `url=` option and not a `front=` option. The check at https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/blob/4fa43a889...The changes in !182 caused a regression for client configurations that only provide a `url=` option and not a `front=` option. The check at https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/blob/4fa43a88927e42fb2e3864f706d3e3c72fd0dca3/client/lib/rendezvous_http.go#L49 is never false, causing a connection to a blank URL to happen if no front is provided:
```
2023/10/26 14:46:44 Negotiating via HTTP rendezvous...
2023/10/26 14:46:44 Target URL: snowflake-broker.torproject.net
2023/10/26 14:46:44 Front URL:
2023/10/26 14:46:44 WebRTC: closing DataChannel
2023/10/26 14:46:44 WebRTC: closing PeerConnection
2023/10/26 14:46:44 WebRTC: Closing
2023/10/26 14:46:44 WebRTC: dial tcp :443: connect: connection refused Retrying...
```Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/issues/28WebTunnel does not connect2023-10-24T16:35:16ZdinosmWebTunnel does not connectI cannot connect to Tor via WebTunnel. I am using Tor Alpha. My connection log is below.
```
2023-10-24 09:50:15.658 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing...I cannot connect to Tor via WebTunnel. I am using Tor Alpha. My connection log is below.
```
2023-10-24 09:50:15.658 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-10-24 09:50:22.472 [NOTICE] Renaming old configuration file to "D:\Utils\Tor Browser\Alpha\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
2023-10-24 09:50:36.887 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-10-24 09:50:36.887 [NOTICE] Switching to guard context "bridges" (was using "default")
2023-10-24 09:50:37.181 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2023-10-24 09:50:37.181 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2023-10-24 09:50:37.599 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
2023-10-24 09:50:37.611 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
2023-10-24 09:50:38.348 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
2023-10-24 09:50:38.466 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
2023-10-24 09:50:38.591 [WARN] Tried connecting to router at [2001:db8:c84d:9331:7c61:633b:6bdb:b352]:443 ID=<none> RSA_ID=945C8C659224ADD3C8AB99BDA5CB6178B6F55AFE, but RSA + ed25519 identity keys were not as expected: wanted 945C8C659224ADD3C8AB99BDA5CB6178B6F55AFE + no ed25519 key but got 719C8B27643CD9283DE52C45112EA61CD45B0D80 + wllgI7D+012eycMYn2wWtIbg+oKDwJgiN5YWjjL5X6o.
2023-10-24 09:50:38.591 [WARN] Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (Unexpected identity in router certificate; IDENTITY; count 1; recommendation warn; host 945C8C659224ADD3C8AB99BDA5CB6178B6F55AFE at 2001:db8:c84d:9331:7c61:633b:6bdb:b352:443)
2023-10-24 09:50:38.599 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
2023-10-24 09:50:38.599 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-10-24 09:50:38.968 [WARN] Managed proxy "N/A" process terminated with status code 0
```https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/issues/27IPv6 only on bridges web site2023-11-02T11:44:51ZJacobo NájeraIPv6 only on bridges web siteOn the site of the bridge, they only appear with IPv6 even when the bridges are only configured for IPv4
https://bridges.torproject.org/bridges/?transport=webtunnel
Thanks, JacoboOn the site of the bridge, they only appear with IPv6 even when the bridges are only configured for IPv4
https://bridges.torproject.org/bridges/?transport=webtunnel
Thanks, Jacobohttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/issues/26WebTunnel Bridge documentation2024-01-08T06:22:39ZJacobo NájeraWebTunnel Bridge documentationHi,
I think the documentation needs to mention the nginx.conf configuration about HTTP upgrade connection (https://community.torproject.org/relay/setup/webtunnel/):
```
#WebSocket Support
map $http_upgrade $connection_up...Hi,
I think the documentation needs to mention the nginx.conf configuration about HTTP upgrade connection (https://community.torproject.org/relay/setup/webtunnel/):
```
#WebSocket Support
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
```
Thanks, Jacobohttps://gitlab.torproject.org/tpo/anti-censorship/gettor-project/OnionSproutsBot/-/issues/54JSONDecodeError when downloading TB2023-10-23T14:11:15Zmeskiomeskio@torproject.orgJSONDecodeError when downloading TBIt fails for linux64 and windows64, but not for others:
```
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Binary (windows-x86_64) requested.
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Expecting value: line 1 column 1 (...It fails for linux64 and windows64, but not for others:
```
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Binary (windows-x86_64) requested.
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Expecting value: line 1 column 1 (char 0)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Traceback (most recent call last):
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/home/telegrambot/venv/lib/python3.9/site-packages/requests/models.py", line 971, in json
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: return complexjson.loads(self.text, **kwargs)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/usr/lib/python3.9/json/__init__.py", line 346, in loads
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: return _default_decoder.decode(s)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/usr/lib/python3.9/json/decoder.py", line 337, in decode
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/usr/lib/python3.9/json/decoder.py", line 355, in raw_decode
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: raise JSONDecodeError("Expecting value", s, err.value) from None
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: During handling of the above exception, another exception occurred:
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: Traceback (most recent call last):
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/home/telegrambot/venv/lib/python3.9/site-packages/pyrogram/dispatcher.py", line 240, in handler_worker
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: await handler.callback(self.client, *args)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/home/telegrambot/onionsproutsbot/OnionSproutsBot/plugins/tor_browser.py", line 113, in download_tor
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: bin_url, bin_name, sig_url, sig_name = latest_download_urls(platform)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/home/telegrambot/onionsproutsbot/OnionSproutsBot/plugins/tor_browser.py", line 46, in latest_download_urls
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: download = session.get(f"{data['tor']['endpoint']}/download-{platform}.json").json()
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: File "/home/telegrambot/venv/lib/python3.9/site-packages/requests/models.py", line 975, in json
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
Oct 23 11:31:46 telegram-bot-01 launch_osbtg[340333]: requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
```Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetmeskiomeskio@torproject.orgmeskiomeskio@torproject.org