Skip to content

How should the Tor service be correctly started so that the search engine can function properly? #138

Description

@Rgwww

Obtain the bridging addresses for obfs4 and webtunnel from the Tor Bridges tg channel. Mount the torrc file on the host machine with the following content:
Log notice file /var/log/tor/notices.log

UseBridges 1

Bridge obfs4 95.217.11.29:22134 9859875C752128125D3179F90BA6351744B09040 cert=W+qSHr6JcFY6UyJiXR3Ec5I5bYHFwDAXNq8HRQU3C56h/aJB8PQqbr8Sq04zKvhEWGbxEw iat-mode=0
Bridge obfs4 51.68.81.140:2098 F205CB5B969389061477609F8E03470B982F64C1 cert=6hFyrclX8Cg16jHGbtYqZxbGxj+p0flBn2EYZu+hvx/tGL4GROXSvBtwVQ1sRYFbi0++fQ iat-mode=0

ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy

SocksPort 0.0.0.0:9050
SocksPolicy accept *

Container log is as follows:

Image

I tried many obfs4 relay addresses, but all of them were invalid. Webtunnel can be correctly configured and accessed on the Tor browser for Windows to access DuckDuckGo, but it seems that the relay address of Webtunnel does not support this.

Are there any good ways to ensure that the search engine of the Tor service can function properly?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions