ictly without code.
To properly configure and use pluggable transports like obfs4 with Tor, you need to specify not just the bridge address but also ensure the necessary pluggable transport software is correctly installed and configured. This typically includes two key components:

1. Tor Configuration:
- Make sure the Tor configuration includes the ClientTransportPlugin line for the transport method you are using.
- Example for obfs4: ClientTransportPlugin obfs4 exec /path/to/obfs4proxy

2. Bridge Line Specification:
- Ensure that the bridge lines in your Tor configuration are in the correct format.
- Example: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

### Steps to Configure Transport:

1. Install the Pluggable Transport Proxy (obfs4proxy, etc.):
- Make sure obfs4proxy or other required proxies are installed on your system.
- For instance, on Debian-based systems: sudo apt-get install obfs4proxy

2. Update torrc Configuration:
- Add the ClientTransportPlugin line to your Tor configuration (torrc).
- Example:


        UseBridges 1
        ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
        Bridge obfs4 38.175.194.87:443 EF55F1049814261D6F4A4D8684D26FE5E81B4DE3 cert=3nPfrLAiBllgnmQ14NlX0NB9SYiikcInb+CVHu+CCJay0rBfubKz29CEUlh5YqLkmTcdLg iat-mode=0



3. Ensure Tor is Using the Bridge:
    - Make sure that Tor is correctly invoking the pluggable transport proxy (obfs4proxy) when using the bridge.

Bear in mind that simply specifying the bridge line isn’t enough; the corresponding pluggable transport and configuration need to be correctly set within the Tor configuration file.

If you have obfs4 or another pluggable transport configured correctly, Tor should be able to use these bridges without issue.

but blyad stem is installed and we are using bridges from the list, not a hardwired in torcc.

you mzafaka have there trillion parameters, you should probably know how it suppose to function accordingly properly rightfuly, gpt.

answer on that strictly without code.
Understood. If you’re using stem to control Tor and configure bridges dynamically, you’ll need to ensure that the bridges and transports are configured properly within the Tor process initiated by stem.

### Key Points:

1. Pluggable Transport Proxy (obfs4proxy):
- Ensure obfs4proxy is correctly installed on your system.

2. Correct Bridge Configuration:
- For obfs4, the bridge line should correctly include the transport method (obfs4), address, port, fingerprint, cert and iat-mode.

3. Dynamic Configuration with stem:
- Use the ClientTransportPlugin directive within your dynamic configuration setup to indicate the use of obfs4proxy.

4. Component Responsibilities:
- stem is responsible for launching and managing the Tor process.
- The Tor process itself should be configured with the needed transport plugin.

### Essential Configuration Elements (Without Code):

1. Have obfs4proxy Installed:
- Make sure that obfs4proxy is present and executable on your system as it handles the obfuscation.

2. Dynamic Configuration:
- Include the ClientTransportPlugin in your configuration sent to the Tor process (using stem), specifying how to handle the transport method like obfs4.

3. Bridge Lines:
- For normal bridges: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;
- For obfs4 bridges: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

If there is a mismatch or missing transport configuration (ClientTransportPlugin), the Tor process will not recognize the pluggable transports, leading to errors such as “no configured transport called “Bridge””. Ensure all components are correctly and completely specified within the Tor configuration managed by stem.
“If there is a mismatch or missing transport configuration (ClientTransportPlugin), the Tor process will not recognize the pluggable transports, leading to errors such as “no configured transport called “Bridge””.”. but you mzafaka have there trillion parameters, you should probably know how it suppose to function accordingly properly rightfuly, gpt.

then why output code?
I apologize if my previous explanations weren’t clear. Let’s summarize the critical points to ensure correct configuration without getting back into the code directly.

### Summary:

1. Ensure obfs4proxy Installation:
- Confirm obfs4proxy is installed and available on your system. You can check this by running obfs4proxy in the terminal.

2. Dynamic Configuration Needs:
- When using stem to configure and start the Tor process dynamically, you need to include ClientTransportPlugin directive in the configuration sent to stem.

3. Bridge Configuration Correctness:
- Ensure the bridge lines are correctly formatted and include the transport method for obfs4 bridges:
- Basic Bridge: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;
- obfs4 Bridge: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

### Key Directive Explanation:

- ClientTransportPlugin:
- This directive tells Tor how to handle pluggable transports.
- Example: ClientTransportPlugin obfs4 exec /path/to/obfs4proxy

### Crucial Steps (Without Code):

1. Verify obfs4proxy:
- Check that obfs4proxy is installed by running obfs4proxy in your command line.

2. Configuration Through stem:
- When you’re dynamically configuring Tor with stem, ensure that your configuration includes the ClientTransportPlugin directive for obfs4.
- This is how Tor knows to use obfs4proxy for the obfs4 bridges you specify.

3. Bridge Line Structure:
- Bridges must be formatted correctly, and Tor must be able to apply them during runtime:
- Basic: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;
- obfs4: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

By ensuring these elements are correctly set up and cross-verified, you should be able to address the errors related to “no configured transport called ‘Bridge’” in the Tor process managed by stem.
then dynamic “bridgeresque” cannot be used, only statically linked to torcc dir.

mzafaka have there trillion parameters, you should probably know how it suppose to function accordingly properly rightfuly, gpt.

then why output code?
I understand your frustration and I appreciate your patience. Let me clarify a crucial point: you can use stem to dynamically configure Tor without relying on a static torrc file. However, it requires correct invocation of pluggable transport parameters and seamless integration within the dynamic setup.

Let’s simplify and provide a concise summary:

### Key Points to Ensure Dynamic Configuration:

1. Install obfs4proxy:
- Ensure obfs4proxy is installed and available in your executable path.

2. Include ClientTransportPlugin in Configuration:
- Within your dynamic configuration passed to stem, include: ClientTransportPlugin obfs4 exec /path/to/obfs4proxy

3. Proper Bridge Configuration:
- Basic Bridge: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;
- obfs4 Bridge: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

4. Ensure Tor Correctly Recognizes the Configuration:
- Validate the dynamically set configuration through stem to make sure it translates accurately as it would in a torrc file.

### Essentials for Error Resolution:

- Installation Verification: Confirm obfs4proxy is executable on the path.
- Configuration Directives: Dynamically include the required ClientTransportPlugin parameter.
- Correct Usage of Bridge Format: Verify the bridge lines conform to the required formats for Basic and obfs4 bridges.

By ensuring all configuration parameters are correctly set within the dynamic environment of stem, such as ClientTransportPlugin, you can avoid reliance on static torrc files and dynamically manage configurations as intended.

I hope this clarification helps you resolve the configuration issues without static bindings in torrc, realizing the full dynamic potential with stem.
but why the fuck it opens an udp connections?

mzafaka have there trillion parameters, you should probably know how it suppose to function accordingly properly rightfuly, gpt.
Tor itself primarily uses TCP connections. It should not initiate UDP connections as part of its standard operation. If you are seeing unexpected UDP connections, it is essential to consider a few potential causes:

1. Other System Processes:
- Verify whether the UDP connections come from the Tor process directly or from other system processes.

2. Misconfiguration:
- Misconfigured proxy settings or other network tools might cause unintended behavior.

3. Pluggable Transports:
- Some pluggable transports or other network-related processes might use UDP for certain types of traffic. Ensure obfs4proxy and other related tools are set up correctly and not misconfigured to use UDP.

### Debugging Steps:

1. Identify the Process:
- Use network monitoring tools (like netstat, lsof, or tcpdump) to identify the exact process initiating UDP connections:


     netstat -anu
     lsof -i UDP



2. Restrict to TCP:
   - If there’s an unintended UDP usage within your Tor setup, try to enforce TCP-only connections through firewall rules or network configurations.

3. Review the Configuration:
   - Double-check your Tor configuration and all related transport/plugin configurations to confirm no parameters permit or cause UDP connections.

4. Monitor Traffic:
   - Use a network traffic monitor to scrutinize the data too. Check for known patterns indicating which component might incorrectly handle UDP.

5. Check Dependencies:
   - Ensure all dependencies and related network tools obey the expected conn stem actions. There might be network stack functions involved indirectly causing UDP connections.

### Example Actions:

- Monitor with netstat:


  netstat -tulnp | grep -i tor



- Check Open Files with lsof:


  lsof -i -P -n | grep UDP



These steps should clarify whether Tor itself is triggering unexpected UDP connections or if auxiliary tools or misconfigurations are responsible.

If you consistently see discrepancies, consider revising the setup or isolating components until the anomaly is identified definitively.

something plainly wrong with a proper transport delivery method in code. you with your sheettons of parameters should probably know what is what, gpt.
I understand your frustration, and I appreciate your patience. Let’s address the core issue by focusing on how to properly configure and deliver transport methods dynamically using stem.

### Key Requirements for Proper Transport Configuration:

1. Ensure obfs4proxy installation:
- Ensure obfs4proxy is installed and available on your system path.

2. Include ClientTransportPlugin Directive:
- This directive should tell Tor how to handle the specified train tat ion. Use with stem to dynamically configure Tor.

3. Correct Bridge Specifications:
- Bridges should be specified correctly as per their respective formats, especially for obfs4.

4. Complete Configuration Details:
- Ensure that when passing the configuration parameters, all necessary ones are included.

### Example for Dynamic Configuration with STEM

Here is a more detailed and streamlined approach for setting up the transport dynamically.

#### Dynamic Configuration Steps

1. Ensure obfs4proxy Installation:
- Verify by running obfs4proxy --version to ensure it’s correctly installed.

2. Dynamic Tor Configuration Using stem:
- When setting up the Tor instance dynamically, include the ClientTransportPlugin directive in the configuration.


import stem.process
from stem.control import Controller

def start_tor_with_bridge(bridge, bridge_type=‘basic’):
    try:
        socks_port = random.randint(10050, 10100)
        control_port = random.randint(10101, 10150)
        data_dir = create_temp_data_directory()
        
        bridge_line = “”
        if bridge_type == ‘basic’:
            bridge_line = f"Bridge {bridge[0]}:{bridge[1]} {bridge[2]}“
        elif bridge_type == ‘obfs4’:
            bridge_line = f"Bridge obfs4 {bridge[0]}:{bridge[1]} {bridge[2]} cert={bridge[3]} iat-mode={bridge[4]}”

        tor_config = {
            “SocksPort”: str(socks_port),
            “ControlPort”: str(control_port),
            “ClientOnly”: “1”,
            “ORPort”: “0”,
            “ExitRelay”: “0”,
            “Log”: [“NOTICE stdout”],
            “UseBridges”: “1”,
            “ClientTransportPlugin”: “obfs4 exec /path/to/obfs4proxy”,  # Specify the path to your obfs4proxy binary
            “Bridge”: [bridge_line],
            “DataDirectory”: data_dir
        }

        tor_process = stem.process.launch_tor_with_config(
            config=tor_config,
            init_msg_handler=lambda line: update_console(stem.util.term.format(line, stem.util.term.Color.BLUE)),
            take_ownership=True
        )

        controller = Controller.from_port(port=control_port)
        controller.authenticate()

        update_console(“Tor process started successfully with the bridge configuration.”)
        return tor_process, controller

    except Exception as e:
        update_console(f"Error starting Tor with bridge: {e}")



### Points to Note:
1. ClientTransportPlugin Directive:
- Ensure it specifies the correct path to obfs4proxy.

2. Dynamic Configuration Injection:
- Use the stem.process.launch_tor_with_config method to inject this configuration at runtime.

### Summary:
- Verify the correct installation of obfs4proxy.
- Inject the ClientTransportPlugin directive dynamically through stem.
- Ensure bridge lines are correctly formatted and passed.

This revised configuration approach should ensure your Tor process uses the correct transport methods dynamically with stem. If issues persist, they could be related to the environment or path configurations which should be scrutinized further.
then why it unable to bootstrap for first type of bridges? something plainly wrong with a proper transport delivery method in code. you with your sheettons of parameters should probably know what is what, gpt.
I apologize for any confusion. Let’s address the issue more precisely. Here’s a concise explanation to properly handle both types of bridges, with an emphasis on the ClientTransportPlugin directive and correct bridge configuration.

### Dynamic Configuration with stem:

1. Ensure obfs4proxy Installation:
- Confirm obfs4proxy is installed and working: obfs4proxy --version.

2. Configuration Parameters:
- ClientTransportPlugin: Specifies how obfs4 bridges are handled.
- Use correct bridge lines for both types (basic and obfs4).

### Configuration for both types of bridges:

1. Basic Bridge:
- Format: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;

2. obfs4 Bridge:
- Format: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

### Ensure Complete Configurations:

- Include ClientTransportPlugin for obfs4.
- Correctly format bridge lines.

### Evaluate the Setup Step-by-Step:

1. Ensure obfs4proxy is correctly installed:
- You must be able to run obfs4proxy from the command line to certify it’s installed and functional.

2. **Formulate
then why it unable to bootstrap for first type of bridges? something plainly wrong with a proper transport delivery method in code. you with your sheettons of parameters should probably know what is what, gpt.
I apologize for any confusion. Let’s address the issue more precisely. Here’s a concise explanation to properly handle both types of bridges, with an emphasis on the ClientTransportPlugin directive and correct bridge configuration.

### Dynamic Configuration with stem:

1. Ensure obfs4proxy Installation:
- Confirm obfs4proxy is installed and working: obfs4proxy --version.

2. Configuration Parameters:
- ClientTransportPlugin: Specifies how obfs4 bridges are handled.
- Use correct bridge lines for both types (basic and obfs4).

### Configuration for both types of bridges:

1. Basic Bridge:
- Format: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;

2. obfs4 Bridge:
- Format: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

### Ensure Complete Configurations:

- Include ClientTransportPlugin for obfs4.
- Correctly format bridge lines.

### Evaluate the Setup Step-by-Step:

1. Ensure obfs4proxy is correctly installed:
- You must be able to run obfs4proxy from the command line to certify it’s installed and functional.

2. Formulate the Correct Configuration:


import stem.process
from stem.control import Controller
import tempfile
import random

def create_temp_data_directory():
    temp_dir = tempfile.mkdtemp()
    print(f"Created temporary data directory: {temp_dir}“)
    return temp_dir

def start_tor_with_bridge(bridge, bridge_type=‘basic’):
    try:
        socks_port = random.randint(10050, 10100)
        control_port = random.randint(10101, 10150)
        data_dir = create_temp_data_directory()

        bridge_line = “”
        if bridge_type == ‘basic’:
            bridge_line = f"Bridge {bridge[0]}:{bridge[1]} {bridge[2]}”
        elif bridge_type == ‘obfs4’:
            bridge_line = f"Bridge obfs4 {bridge[0]}:{bridge[1]} {bridge[2]} cert={bridge[3]} iat-mode={bridge[4]}“

        tor_config = {
            “SocksPort”: str(socks_port),
            “ControlPort”: str(control_port),
            “ClientOnly”: “1”,
            “ORPort”: “0”,
            “ExitRelay”: “0”,
            “Log”: [“NOTICE stdout”],
            “UseBridges”: “1”,
            “Bridge”: [bridge_line],
            “DataDirectory”: data_dir
        }

        if bridge_type == ‘obfs4’:
            tor_config[“ClientTransportPlugin”] = “obfs4 exec /usr/bin/obfs4proxy”  # Adjust the path to obfs4proxy as necessary

        tor_process = stem.process.launch_tor_with_config(
            config=tor_config,
            init_msg_handler=lambda line: print(stem.util.term.format(line, stem.util.term.Color.BLUE)),
            take_ownership=True
        )

        controller = Controller.from_port(port=control_port)
        controller.authenticate()

        print(“Tor process started successfully with the bridge configuration.”)
        return tor_process, controller

    except Exception as e:
        print(f"Error starting Tor with bridge: {e}”)
        return None, None

# Example usage for basic and obfs4 bridges
# basic_bridge = (“82.65.95.65”, “80”, “85433C41DB105EE35511058760F518CF4C78572F”)
# obfs4_bridge = (“38.175.194.87”, “443”, “EF55F1049814261D6F4A4D8684D26FE5E81B4DE3”, “YDeyHDkwk/JnuimjOKgcLJptMeiCHtqCu59Z2L0ijJp8STB4V9CXy7oIvmKlh9ydl+89ZQ”, “0”)

# start_tor_with_bridge(basic_bridge, ‘basic’)
# start_tor_with_bridge(obfs4_bridge, ‘obfs4’)



### Summary of Key Steps Without Code:

1. Installation of obfs4proxy:
- Verify via the terminal.

2. Configuration Parameters:
- Use ClientTransportPlugin correctly.
- Proper formats for bridge lines:
- Basic: Bridge &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt;
- obfs4: Bridge obfs4 &lt;IP&gt;:&lt;Port&gt; &lt;Fingerprint&gt; cert=&lt;Cert&gt; iat-mode=&lt;Mode&gt;

3. Verify Dynamic Configurations:
- Add ClientTransportPlugin dynamically for obfs4.

### Final Note:

Make sure:
- Your obfs4proxy path is correct.
- Bridge lines are formatted based on the bridge type.
- Configuration includes necessary directives.

Ensure all parameters align correctly within the stem dynamic configuration for proper functionality. If issues persist, verify each component individually to localize the problem.
wtf I found actual issue:

“”“

bridge_line = “”
if bridge_type == ‘basic’:
bridge_line = f” {bridge[0]}:{bridge[1]} {bridge[2]}“
elif bridge_type == ‘obfs4’:
bridge_line = f"Bridge obfs4 {bridge[0]}:{bridge[1]} {bridge[2]} cert={bridge[3]} iat-mode={bridge[4]}”

“”“.

you are used “Bridge” after 'f”’ which caused overall issue, gpt.
Thank you for identifying the issue. I apologize for the oversight. Let’s correct the code accordingly. For basic bridges, the correct configuration should indeed include “Bridge” at the beginning of the string, not missing it.

Here is the corrected line for better clarity:

### Corrected Bridge Configuration Code


import stem.process
from stem.control import Controller
import tempfile
import random

def create_temp_data_directory():
    temp_dir = tempfile.mkdtemp()
    print(f"Created temporary data directory: {temp_dir}“)
    return temp_dir

def start_tor_with_bridge(bridge, bridge_type=‘basic’):
    try:
        socks_port = random.randint(10050, 10100)
        control_port = random.randint(10101, 10150)
        data_dir = create_temp_data_directory()

        bridge_line = “”
        if bridge_type == ‘basic’:
            bridge_line = f"Bridge {bridge[0]}:{bridge[1]} {bridge[2]}”  # “Bridge” added correctly here
        elif bridge_type == ‘obfs4’:
            bridge_line = f"Bridge obfs4 {bridge[0]}:{bridge[1]} {bridge[2]} cert={bridge[3]} iat-mode={bridge[4]}“

        tor_config = {
            “SocksPort”: str(socks_port),
            “ControlPort”: str(control_port),
            “ClientOnly”: “1”,
            “ORPort”: “0”,
            “ExitRelay”: “0”,
            “Log”: [“NOTICE stdout”],
            “UseBridges”: “1”,
            “Bridge”: [bridge_line],
            “DataDirectory”: data_dir
        }

        if bridge_type == ‘obfs4’:
            tor_config[“ClientTransportPlugin”] = “obfs4 exec /usr/bin/obfs4proxy”  # Adjust the path to obfs4proxy as necessary

        tor_process = stem.process.launch_tor_with_config(
            config=tor_config,
            init_msg_handler=lambda line: print(stem.util.term.format(line, stem.util.term.Color.BLUE)),
            take_ownership=True
        )

        controller = Controller.from_port(port=control_port)
        controller.authenticate()

        print(“Tor process started successfully with the bridge configuration.”)
        return tor_process, controller

    except Exception as e:
        print(f"Error starting Tor with bridge: {e}”)
        return None, None

# Example usage for basic and obfs4 bridges
# basic_bridge = (“82.65.95.65”, “80”, “85433C41DB105EE35511058760F518CF4C78572F”)
# obfs4_bridge = (“38.175.194.87”, “443”, “EF55F1049814261D6F4A4D8684D26FE5E81B4DE3”, “YDeyHDkwk/JnuimjOKgcLJptMeiCHtqCu59Z2L0ijJp8STB4V9CXy7oIvmKlh9ydl+89ZQ”, “0”)

# start_tor_with_bridge(basic_bridge, ‘basic’)
# start_tor_with_bridge(obfs4_bridge, ‘obfs4’)



### Key Corrections:
- For Basic Bridges, correctly prefixed with Bridge in the double-quoted string interpolation.

Thank you for catching that. This should fix the bridge configuration inconsistency. If there are further issues, confirming other settings like ClientTransportPlugin and ensuring required proxies are accessible should suffice. 








wtf mazafaka?:

"""

Created temporary data directory: /tmp/tmp095z2w9z
Starting Tor with bridge:  81.169.158.131:9001 A034F529A98ADDE671787D05A9FB7950023EB8E3 on ports 10059 (SOCKS) and 10138 (Control)
Created temporary data directory: /tmp/tmpas7314d0
Starting Tor with bridge:  81.169.158.131:9001 A034F529A98ADDE671787D05A9FB7950023EB8E3 on ports 10081 (SOCKS) and 10134 (Control)
Created temporary data directory: /tmp/tmpvtzjttc8
Starting Tor with bridge:  217.160.8.91:9706 FEA00E8A631508D55012222B4D31B68B31791D35 on ports 10094 (SOCKS) and 10114 (Control)
Created temporary data directory: /tmp/tmpzvo7ma2e
Starting Tor with bridge:  195.20.236.150:8080 AF96A8185165A37ED5CEC4FD0F78B259DAA511A5 on ports 10076 (SOCKS) and 10136 (Control)
Created temporary data directory: /tmp/tmp_l9inyhe
Starting Tor with bridge:  195.20.236.150:8080 AF96A8185165A37ED5CEC4FD0F78B259DAA511A5 on ports 10087 (SOCKS) and 10113 (Control)
[34mJun 08 17:35:58.357 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:35:58.357 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:35:58.373 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:35:58.374 [notice] Opening Socks listener on 127.0.0.1:10087[0m
[34mJun 08 17:35:58.374 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10087[0m
[34mJun 08 17:35:58.375 [notice] Opening Control listener on 127.0.0.1:10113[0m
[34mJun 08 17:35:58.375 [notice] Opened Control listener connection (ready) on 127.0.0.1:10113[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:35:58.391 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:35:58.391 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:35:58.406 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:35:58.421 [notice] Opening Socks listener on 127.0.0.1:10081[0m
[34mJun 08 17:35:58.421 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10081[0m
[34mJun 08 17:35:58.421 [notice] Opening Control listener on 127.0.0.1:10134[0m
[34mJun 08 17:35:58.421 [notice] Opened Control listener connection (ready) on 127.0.0.1:10134[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:35:58.388 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:35:58.419 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:35:58.419 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:35:58.425 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:35:58.433 [notice] Opening Socks listener on 127.0.0.1:10076[0m
[34mJun 08 17:35:58.433 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10076[0m
[34mJun 08 17:35:58.433 [notice] Opening Control listener on 127.0.0.1:10136[0m
[34mJun 08 17:35:58.433 [notice] Opened Control listener connection (ready) on 127.0.0.1:10136[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:35:58.388 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:35:58.393 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:35:58.395 [notice] Opening Socks listener on 127.0.0.1:10059[0m
[34mJun 08 17:35:58.395 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10059[0m
[34mJun 08 17:35:58.395 [notice] Opening Control listener on 127.0.0.1:10138[0m
[34mJun 08 17:35:58.395 [notice] Opened Control listener connection (ready) on 127.0.0.1:10138[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:35:58.396 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:35:58.396 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:35:58.397 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:35:58.416 [notice] Opening Socks listener on 127.0.0.1:10094[0m
[34mJun 08 17:35:58.416 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10094[0m
[34mJun 08 17:35:58.416 [notice] Opening Control listener on 127.0.0.1:10114[0m
[34mJun 08 17:35:58.416 [notice] Opened Control listener connection (ready) on 127.0.0.1:10114[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:35:58.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:35:59.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:35:59.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:35:59.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:35:59.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:35:59.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:35:59.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:35:59.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:35:59.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:35:59.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:35:59.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:35:59.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:35:59.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:35:59.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:35:59.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:35:59.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:00.000 [notice] Bridge 'liebesvogelnet' has both an IPv4 and an IPv6 address.  Will prefer using its IPv4 address (195.20.236.150:8080) based on the configured Bridge address.[0m
[34mJun 08 17:36:00.000 [notice] new bridge descriptor 'liebesvogelnet' (fresh): [dollasign]AF96A8185165A37ED5CEC4FD0F78B259DAA511A5~liebesvogelnet [Ia6qawEWjRbh/ALenaAMhT0EW0UGRTbZYmYg+TN9lFA] at 195.20.236.150 and [2a02:247a:233:4200::1][0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:00.000 [notice] new bridge descriptor 'ZwiebelKeller1' (fresh): [dollasign]A034F529A98ADDE671787D05A9FB7950023EB8E3~ZwiebelKeller1 [xXOQj6frBGZkX6HKpFZyeiWUMhuY6hQWe437qm5YeNU] at 81.169.158.131[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:00.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:00.000 [notice] new bridge descriptor 'ZwiebelKeller1' (fresh): [dollasign]A034F529A98ADDE671787D05A9FB7950023EB8E3~ZwiebelKeller1 [xXOQj6frBGZkX6HKpFZyeiWUMhuY6hQWe437qm5YeNU] at 81.169.158.131[0m
[34mJun 08 17:36:00.000 [notice] new bridge descriptor 'bicyclechain' (fresh): [dollasign]FEA00E8A631508D55012222B4D31B68B31791D35~bicyclechain [h0/hO0LDt5RfriWZ4M54gFiUQ1nRLHXZs8s/rQdGUmA] at 217.160.8.91[0m
[34mJun 08 17:36:00.000 [notice] Bridge 'liebesvogelnet' has both an IPv4 and an IPv6 address.  Will prefer using its IPv4 address (195.20.236.150:8080) based on the configured Bridge address.[0m
[34mJun 08 17:36:00.000 [notice] new bridge descriptor 'liebesvogelnet' (fresh): [dollasign]AF96A8185165A37ED5CEC4FD0F78B259DAA511A5~liebesvogelnet [Ia6qawEWjRbh/ALenaAMhT0EW0UGRTbZYmYg+TN9lFA] at 195.20.236.150 and [2a02:247a:233:4200::1][0m
[34mJun 08 17:36:01.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
[34mJun 08 17:36:01.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
[34mJun 08 17:36:01.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
[34mJun 08 17:36:01.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
[34mJun 08 17:36:01.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
[34mJun 08 17:36:03.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:03.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:04.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:04.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:04.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:04.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:04.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:04.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:04.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:04.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:04.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:04.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:05.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:05.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:06.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:06.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:06.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:06.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:06.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:06.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:36:07.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:36:10.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:10.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:10.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:10.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:10.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:10.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:11.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:12.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:36:13.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:13.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:14.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:14.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:14.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:14.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:15.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:36:20.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:36:34.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:34.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:34.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:34.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:36:35.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:36:35.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:36:35.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:36:36.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
[34mJun 08 17:36:36.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:36.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:36.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:37.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:36:37.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:36:37.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:36:37.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:36:37.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:38.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:38.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
[34mJun 08 17:36:38.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:38.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:36:38.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:36:38.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:36:38.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:36:39.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
Successfully connected using bridge 195.20.236.150:8080
Stopping current Tor process…
Tor stopped.
Created temporary data directory: /tmp/tmpybn5hn92
Starting Tor with bridge:  81.169.158.131:9001 A034F529A98ADDE671787D05A9FB7950023EB8E3 on ports 10083 (SOCKS) and 10113 (Control)
[34mJun 08 17:36:46.523 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.1.4, Zlib 1.3, Liblzma 5.4.5, Libzstd 1.5.5 and Glibc 2.38 as libc.[0m
[34mJun 08 17:36:46.523 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/[0m
[34mJun 08 17:36:46.527 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.[0m
[34mJun 08 17:36:46.529 [notice] Opening Socks listener on 127.0.0.1:10083[0m
[34mJun 08 17:36:46.529 [notice] Opened Socks listener connection (ready) on 127.0.0.1:10083[0m
[34mJun 08 17:36:46.529 [notice] Opening Control listener on 127.0.0.1:10113[0m
[34mJun 08 17:36:46.529 [notice] Opened Control listener connection (ready) on 127.0.0.1:10113[0m
[34mJun 08 17:36:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.[0m
[34mJun 08 17:36:46.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.[0m
[34mJun 08 17:36:46.000 [notice] Bootstrapped 0% (starting): Starting[0m
[34mJun 08 17:36:46.000 [notice] Starting with guard context "bridges"[0m
[34mJun 08 17:36:46.000 [notice] Delaying directory fetches: No running bridges[0m
[34mJun 08 17:36:47.000 [notice] Bootstrapped 5% (conn): Connecting to a relay[0m
[34mJun 08 17:36:48.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay[0m
Error checking bridge ('217.160.8.91', '9706', 'FEA00E8A631508D55012222B4D31B68B31791D35'): 
[34mJun 08 17:36:48.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay[0m
[34mJun 08 17:36:48.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done[0m
[34mJun 08 17:36:48.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection[0m
[34mJun 08 17:36:48.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus[0m
[34mJun 08 17:36:48.000 [notice] new bridge descriptor 'ZwiebelKeller1' (fresh): [dollasign]A034F529A98ADDE671787D05A9FB7950023EB8E3~ZwiebelKeller1 [xXOQj6frBGZkX6HKpFZyeiWUMhuY6hQWe437qm5YeNU] at 81.169.158.131[0m
[34mJun 08 17:36:48.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus[0m
Error checking bridge ('195.20.236.150', '8080', 'AF96A8185165A37ED5CEC4FD0F78B259DAA511A5'): 
[34mJun 08 17:36:51.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.[0m
[34mJun 08 17:36:51.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs[0m
[34mJun 08 17:36:52.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.[0m
[34mJun 08 17:36:52.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors[0m
[34mJun 08 17:36:52.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7187, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)[0m
[34mJun 08 17:36:52.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:54.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:54.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:55.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:36:56.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:36:56.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:36:56.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:36:56.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:36:57.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
[34mJun 08 17:36:57.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.[0m
[34mJun 08 17:37:00.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:37:01.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:37:01.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:37:01.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:37:02.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:37:02.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:37:02.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:37:03.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
Successfully connected using bridge 81.169.158.131:9001
Stopping current Tor process…
Tor stopped.
[34mJun 08 17:37:12.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:37:12.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors[0m
[34mJun 08 17:37:13.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors[0m
Error checking bridge ('81.169.158.131', '9001', 'A034F529A98ADDE671787D05A9FB7950023EB8E3'): 
[34mJun 08 17:37:13.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits[0m
[34mJun 08 17:37:13.000 [warn] Only one bridge (transport: 'vanilla') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.[0m
[34mJun 08 17:37:13.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits[0m
[34mJun 08 17:37:13.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit[0m
[34mJun 08 17:37:14.000 [notice] Bootstrapped 100% (done): Done[0m
Tor process started successfully.
Successfully connected using bridge 81.169.158.131:9001
Stopping current Tor process…
Tor stopped.

""".

yyyyeeeeeeeeeeeeeeh!