Good day
Problem with tor, snowflake does not connect computer to tor. Same with obfs and webtunnel. Tor Browser connect to tor normally through snowflake. Please help me in this. I want to unblock Telegram calls and WhatsApp. System Linux Mint 22 MATE, OpenSSL 3.0.3 . Also installed OpenSSL 3.6.1 from tar.gz but deactivated after error (see logs)
artem@artem-laptop:\~$ openssl version
OpenSSL 3.6.1 27 Jan 2026 (Library: OpenSSL 3.6.1 27 Jan 2026)
artem@artem-laptop:\~$ journalctl -e -u tor@default
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.178 \[notice\] Read confi>
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.180 \[notice\] Opening So>
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.180 \[notice\] Opened Soc>
фев 12 09:55:55 artem-laptop Tor\[4399\]: OpenSSL version from headers does not m>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Tor 0.4.8.22 running on Linux with Libe>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Tor can’t help you if you use it wrong!>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Read configuration file "/usr/share/tor>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Read configuration file "/etc/tor/torrc>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Opening Socks listener on 127.0.0.1:9050
фев 12 09:55:55 artem-laptop Tor\[4399\]: Opened Socks listener connection (ready>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Parsing GEOIP IPv4 file /usr/share/tor/>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Parsing GEOIP IPv6 file /usr/share/tor/>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Set list of supported TLS groups to: P->
фев 12 09:55:55 artem-laptop Tor\[4399\]: Bootstrapped 0% (starting): Starting
фев 12 09:55:55 artem-laptop Tor\[4399\]: Starting with guard context “default”
фев 12 09:55:55 artem-laptop Tor\[4399\]: Signaled readiness to systemd
фев 12 09:55:55 artem-laptop systemd\[1\]: Started tor@default.service - Anonymiz>
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opening Socks listener on /run/tor/socks
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opened Socks listener connection (ready>
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opening Control listener on /run/tor/co>
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opened Control listener connection (rea>
фев 12 09:55:56 artem-laptop Tor\[4399\]: Bootstrapped 5% (conn): Connecting to a>
фев 12 09:55:56 artem-laptop Tor\[4399\]: Bootstrapped 10% (conn_done): Connected>
lines 127-149/149 (END)
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.178 \[notice\] Read configuration file “/etc/tor/torrc”.
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.180 \[notice\] Opening Socks listener on 127.0.0.1:9050
фев 12 09:55:55 artem-laptop tor\[4399\]: Feb 12 09:55:55.180 \[notice\] Opened Socks listener connection (ready) on 127.0.0.1:9050
фев 12 09:55:55 artem-laptop Tor\[4399\]: OpenSSL version from headers does not match the version we’re running with. If you get weird crashes, that might be why. (Compiled with 30500050: OpenSSL 3.5.5 27 Jan 2026; running with 300000d0: 3>
фев 12 09:55:55 artem-laptop Tor\[4399\]: Tor 0.4.8.22 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.39 as libc.
фев 12 09:55:55 artem-laptop Tor\[4399\]: Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
фев 12 09:55:55 artem-laptop Tor\[4399\]: Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
фев 12 09:55:55 artem-laptop Tor\[4399\]: Read configuration file “/etc/tor/torrc”.
фев 12 09:55:55 artem-laptop Tor\[4399\]: Opening Socks listener on 127.0.0.1:9050
фев 12 09:55:55 artem-laptop Tor\[4399\]: Opened Socks listener connection (ready) on 127.0.0.1:9050
фев 12 09:55:55 artem-laptop Tor\[4399\]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
фев 12 09:55:55 artem-laptop Tor\[4399\]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
фев 12 09:55:55 artem-laptop Tor\[4399\]: Set list of supported TLS groups to: P-256:X25519:P-224
фев 12 09:55:55 artem-laptop Tor\[4399\]: Bootstrapped 0% (starting): Starting
фев 12 09:55:55 artem-laptop Tor\[4399\]: Starting with guard context “default”
фев 12 09:55:55 artem-laptop Tor\[4399\]: Signaled readiness to systemd
фев 12 09:55:55 artem-laptop systemd\[1\]: Started tor@default.service - Anonymizing overlay network for TCP.
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opening Socks listener on /run/tor/socks
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opened Socks listener connection (ready) on /run/tor/socks
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opening Control listener on /run/tor/control
фев 12 09:55:56 artem-laptop Tor\[4399\]: Opened Control listener connection (ready) on /run/tor/control
фев 12 09:55:56 artem-laptop Tor\[4399\]: Bootstrapped 5% (conn): Connecting to a relay
фев 12 09:55:56 artem-laptop Tor\[4399\]: Bootstrapped 10% (conn_done): Connected to a relay
lines 127-149/149 (END)
artem@artem-laptop:\~$ journalctl -e -u tor@default
фев 12 10:15:58 artem-laptop Tor\[6421\]: Parsing GEOIP IPv6 file /usr/share/tor/>
фев 12 10:15:58 artem-laptop Tor\[6421\]: Bootstrapped 0% (starting): Starting
фев 12 10:15:58 artem-laptop Tor\[6421\]: Starting with guard context “default”
фев 12 10:15:58 artem-laptop systemd\[1\]: Started tor@default.service - Anonymiz>
фев 12 10:15:58 artem-laptop Tor\[6421\]: Signaled readiness to systemd
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opening Socks listener on /run/tor/socks
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opened Socks listener connection (ready>
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opening Control listener on /run/tor/co>
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opened Control listener connection (rea>
фев 12 10:15:59 artem-laptop Tor\[6421\]: Bootstrapped 5% (conn): Connecting to a>
фев 12 10:18:00 artem-laptop Tor\[6421\]: Bootstrapped 10% (conn_done): Connected>
фев 12 10:24:59 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (co>
фев 12 10:24:59 artem-laptop Tor\[6421\]: 10 connections have failed:
фев 12 10:24:59 artem-laptop Tor\[6421\]: 7 connections died in state connect()i>
фев 12 10:24:59 artem-laptop Tor\[6421\]: 3 connections died in state handshakin>
фев 12 10:25:03 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (co>
фев 12 10:25:03 artem-laptop Tor\[6421\]: 11 connections have failed:
фев 12 10:25:03 artem-laptop Tor\[6421\]: 7 connections died in state connect()i>
фев 12 10:25:03 artem-laptop Tor\[6421\]: 4 connections died in state handshakin>
фев 12 10:26:14 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (co>
фев 12 10:26:14 artem-laptop Tor\[6421\]: 11 connections have failed:
фев 12 10:26:14 artem-laptop Tor\[6421\]: 7 connections died in state connect()i>
фев 12 10:26:14 artem-laptop Tor\[6421\]: 4 connections died in state handshakin>
lines 207-229/229 (END)
фев 12 10:15:58 artem-laptop Tor\[6421\]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
фев 12 10:15:58 artem-laptop Tor\[6421\]: Bootstrapped 0% (starting): Starting
фев 12 10:15:58 artem-laptop Tor\[6421\]: Starting with guard context “default”
фев 12 10:15:58 artem-laptop systemd\[1\]: Started tor@default.service - Anonymizing overlay network for TCP.
фев 12 10:15:58 artem-laptop Tor\[6421\]: Signaled readiness to systemd
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opening Socks listener on /run/tor/socks
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opened Socks listener connection (ready) on /run/tor/socks
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opening Control listener on /run/tor/control
фев 12 10:15:59 artem-laptop Tor\[6421\]: Opened Control listener connection (ready) on /run/tor/control
фев 12 10:15:59 artem-laptop Tor\[6421\]: Bootstrapped 5% (conn): Connecting to a relay
фев 12 10:18:00 artem-laptop Tor\[6421\]: Bootstrapped 10% (conn_done): Connected to a relay
фев 12 10:24:59 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 10; recommendation warn; host F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 at 131.188.40.189:443)
фев 12 10:24:59 artem-laptop Tor\[6421\]: 10 connections have failed:
фев 12 10:24:59 artem-laptop Tor\[6421\]: 7 connections died in state connect()ing with SSL state (No SSL object)
фев 12 10:24:59 artem-laptop Tor\[6421\]: 3 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
фев 12 10:25:03 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 11; recommendation warn; host 1BD6462B856754E9C826B220B4C47E59D0479109 at 146.59.12.188:9001)
фев 12 10:25:03 artem-laptop Tor\[6421\]: 11 connections have failed:
фев 12 10:25:03 artem-laptop Tor\[6421\]: 7 connections died in state connect()ing with SSL state (No SSL object)
фев 12 10:25:03 artem-laptop Tor\[6421\]: 4 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
фев 12 10:26:14 artem-laptop Tor\[6421\]: Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (Connection timed out; TIMEOUT; count 12; recommendation warn; host 0806B64E53BD3ED2F0BDB5EED8DBF81DF331F45A at 185.241.208.20>
фев 12 10:26:14 artem-laptop Tor\[6421\]: 11 connections have failed:
фев 12 10:26:14 artem-laptop Tor\[6421\]: 7 connections died in state connect()ing with SSL state (No SSL object)
фев 12 10:26:14 artem-laptop Tor\[6421\]: 4 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
lines 207-229/229 (END)
Summary
This text will be hidden
How to install
Check computer arhitecture. It should be amd64
sudo dpkg --print-architecture
sudo apt install apt-transport-https
sudo xed /etc/os-release
NAME=“Linux Mint”
VERSION=“22 (Wilma)”
ID=linuxmint
ID_LIKE=“ubuntu debian”
PRETTY_NAME=“Linux Mint 22”
VERSION_ID=“22”
HOME_URL=“https://www.linuxmint.com/”
SUPPORT_URL=“https://forums.linuxmint.com/”
BUG_REPORT_URL=“http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/”
PRIVACY_POLICY_URL=“https://www.linuxmint.com/”
VERSION_CODENAME=wilma
UBUNTU_CODENAME=noble
sudo xed /etc/apt/sources.list.d/tor.sources
Types: deb deb-src
URIs: https://deb.torproject.org/torproject.org/
Suites:
Components: main
Signed-By: /usr/share/keyrings/deb.torproject.org-keyring.gpg
sudo apt install gnupg
https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc
Save autorisation key to Desktop from Tor Browser and add through GUI (if blocked https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc )
or
wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc | gpg --dearmor | sudo tee /usr/share/keyrings/deb.torproject.org-keyring.gpg >/dev/null
sudo apt update
sudo apt install tor deb.torproject.org-keyring
No need to install new OpenSSL if you install old tor 0.4.7.16 besause it cracks your depends
sudo dpkg -P --force-depends openssl
sudo apt install build-essential checkinstall zlib1g-dev -y
cd /usr/local/src/
sudo wget https://github.com/openssl/openssl/releases/download/openssl-3.6.1/openssl-3.6.1.tar.gz
sudo tar -xf openssl-3.6.1.tar.gz
cd openssl-3.6.1
sudo ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib
sudo make
sudo make test
sudo make install
cd /etc/ld.so.conf.d/
sudo xed openssl-3.6.1.conf
Insert openssl library path directory
/usr/local/ssl/lib64
sudo ldconfig -v
sudo mv /usr/bin/c_rehash /usr/bin/c_rehash.bak
sudo mv /usr/bin/openssl /usr/bin/openssl.bak
sudo xed /etc/environment
before
PATH=“/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin”
edit
PATH=“/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/ssl/bin”
Reload environment file and test updated binary PATH.
source /etc/environment
echo $PATH
which openssl
openssl version
sudo apt --fix-broken install
Install from Debian repository deb installation files libtorsocks_2.5.0-1_amd64.deb ; tor_0.4.8.22-1_amd64.deb ; tor-geoipdb_0.4.8.22-1_all.deb ; torsocks_2.5.0-1_all.deb
If you have error OpenSSL version from headers does not match the version we’re running with. If you get weird crashes, that might be why. (Compiled with 30500050: OpenSSL 3.5.5 27 Jan 2026; running with 300000d0: 3>
so install tor-geoipdb_0.4.7.16-1_all.deb ; tor_0.4.7.16-1_amd64.deb для версии OpenSSL 3.0.3
or if not blocked repository
sudo apt install tor
sudo apt-get install obfs4proxy
systemctl enable --now tor.service
systemctl restart tor.service
sudo xed /etc/tor/torrc
journalctl -e -u tor@default
Config file /etc/tor/torrc
## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what’s going on. Lines
## that begin with just “#” are disabled commands: you can enable them
## by removing the “#” symbol.
##
## See ‘man tor’, or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
##
https://www.torproject.org/docs/faq#torrc
## Tor opens a socks proxy on port 9050 by default – even if you don’t
## configure one below. Set “SocksPort 0” if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
#SocksPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests that reach a SocksPort. Untrusted users who
## can access your SocksPort may be able to learn about the connections
## you make.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject \*
## Logs go to stdout at level “notice” unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using “notice” in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level ‘notice’ or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor’s logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background… or use
## –runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\\tor on Windows.
#DataDirectory /var/lib/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1
############### This section is just for location-hidden services ###
## Once you have configured a hidden service, you can look at the
## contents of the file “…/hidden_service/hostname” for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.
#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.
## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows. You’ll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise
## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com
## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5
## A handle for your relay, so people don’t have to refer to it by key.
#Nickname ididnteditheconfig
## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB.
## Note that units for these config options are bytes per second, not bits
## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.
#RelayBandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting “4 GB” may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00
## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it’s an email address and/or generate a new address for this purpose.
#ContactInfo Random Person
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person
## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows. below too. You’ll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor’s source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html
## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they’re on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
##
https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge’s fingerprint here, as it would
## break its concealability and potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,…
## A comma-separated list of exit policies. They’re considered first
## to last, and the first match wins. If you want to *replace*
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you’re *augmenting* (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## described in the man page or at
##
https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this – otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow “exit enclaving”.
##
#ExitPolicy accept \*:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept \*:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
## Bridge relays (or “bridges”) are Tor relays that aren’t listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won’t be able to block all the bridges. Also, websites won’t treat you
## differently because they won’t know you’re running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## Please review the path to the pluggable transport executable
ClientTransportPlugin meek_lite,obfs4,snowflake,webtunnel exec /home/user/Downloads/tor/pluggable_transports/lyrebird
# Uncomment the line below depending to the type of bridge your are using
#Bridge snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://1098762253.rsc.cdn77.org fronts=www.phpmyadmin.net,cdn.zk.mk ice=stun:stun.antisip.com:3478,stun:stun.epygi.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.mixvoip.com:3478,stun:stun.nextcloud.com:3478,stun:stun.bethesda.net:3478,stun:stun.nextcloud.com:443 utls-imitate=hellorandomizedalpn
#Bridge snowflake 192.0.2.4:80 8838024498816A039FCBBAB14E6F40A0843051FA fingerprint=8838024498816A039FCBBAB14E6F40A0843051FA url=https://1098762253.rsc.cdn77.org fronts=www.phpmyadmin.net,cdn.zk.mk ice=stun:stun.antisip.com:3478,stun:stun.epygi.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.mixvoip.com:3478,stun:stun.nextcloud.com:3478,stun:stun.bethesda.net:3478,stun:stun.nextcloud.com:443 utls-imitate=hellorandomizedalpn