[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #26891 [Obfuscation/meek]: Problem running meek server without CDN, stuck at Performing bandwidth self-test...done
#26891: Problem running meek server without CDN, stuck at Performing bandwidth
self-test...done
------------------------------+---------------------
Reporter: weiruo | Owner: dcf
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Obfuscation/meek | Version:
Severity: Normal | Resolution:
Keywords: meek server | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------------+---------------------
Comment (by dcf):
This is the problem:
{{{
[warn] Server managed proxy encountered a method error. (meek listen tcp
0.0.0.0:443: bind: address already in use)
}}}
Some other process is already listening on port 443. Try `netstat -nlp |
grep :443` to find out what it is.
If, for some reason, you cannot stop the other process from listening on
port 443, you can choose a different port for meek-server with
`ServerTransportListenAddr` (but it is unusual for HTTPS to be on another
port).
> Must I use CDN to domain fronting it?
> By the way, is it possible to use meek without domain fronting if the
domain has not been filtered?
No, you don't need to use domain fronting. Connecting directly to an
unblocked domain is a valid way to use it. In your client torrc, use
`url=...` without `front=...`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26891#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs