Qian Wenjie
Qian Wenjie
Trojan URI in pproxy is not the format "trojan://password@ip:port". It should be "trojan://ip:port#password".
You can read the Trojan example part of README.rst. Trojan protocol is used with ssl in most cases like "trojan+ssl://".
I can't understand the client side part. "-r" is missing in the command line. If you want to use backward, you should use the same protocol. For example, if client...
pproxy can only listen on a port having protocols with ssl or without ssl. Guessing a protocol wrapped in ssl/tls by peeking a few bytes is impossible. It is impossible...
If the client is sending TCP, server and client should use -r and -l instead of -ur and -ul
QUIC is listening on UDP port, but if you want to proxy TCP over QUIC, you should specify -l and -r. QUIC cannot be used standalone. You can use quic+http...
The example I have put in docs should work. What is the error message?
> btw this is the error I get when trying to run the mentioned QUIC client: > >  You should use quic+http:// instead of quic:// here.
>  > > in this screenshot, can you please help me find where did I put the config wrong. it looks like the client never finds the server. Try...
quic connection is very stable and useful for handling multiple streams in a single UDP port. I am using quic everyday. :)