You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 1.1.2
Client
{
"ServerName":"www.oracle.com",
"Key":"XXXXXX",
"TicketTimeHint":3600,
"Browser":"chrome",
"FastOpen":false
}
Server
{
"WebServerAddr":"2.19.128.136:443",
"Key":"XXXXXX",
"FastOpen":false
}
ss-libev run with xchacha20-ietf-poly1305 method.
At first, connection is fine. after about an hour with some traffic (no big download, just some browser), 443 port is blocked in local ISP. Stop client for about a day, 443 port is opened again.
Local ISP is very sensitive that tls1.2 from ssr or tls from simple-obfs is blocked after some traffic too. Only ws over https can work on port 443.
The text was updated successfully, but these errors were encountered:
I think our traffic is still significant in that each TCP connection will lead to a TLS handshake with the proxy server. Frequent handshakes are not normal.
I'm thinking of establishing a fixed amount of standing TLS sessions and multiplex traffic through them.
Version 1.1.2
Client
{
"ServerName":"www.oracle.com",
"Key":"XXXXXX",
"TicketTimeHint":3600,
"Browser":"chrome",
"FastOpen":false
}
Server
{
"WebServerAddr":"2.19.128.136:443",
"Key":"XXXXXX",
"FastOpen":false
}
ss-libev run with xchacha20-ietf-poly1305 method.
At first, connection is fine. after about an hour with some traffic (no big download, just some browser), 443 port is blocked in local ISP. Stop client for about a day, 443 port is opened again.
Local ISP is very sensitive that tls1.2 from ssr or tls from simple-obfs is blocked after some traffic too. Only ws over https can work on port 443.
The text was updated successfully, but these errors were encountered: