nadoo / glider

glider is a forward proxy with multiple protocols support, and also a dns/dhcp server with ipset management features(like dnsmasq).
GNU General Public License v3.0
3.19k stars 439 forks source link

What is the correct way to use https proxy with user/password? #394

Closed danilovsergei closed 6 months ago

danilovsergei commented 1 year ago

I'm trying to connect to https secureconnect.me:7070 proxy , which has user/pass auth

Basically doing pretty much the same as describe in that article: https://torguard.net/indexori.php?rp=/knowledgebase/297/How-to-Connect-with-TorGuardandsharp039s-SSL-Proxy-on-Android.html

But there are not examples of using https with user/password. I tried

./glider -listen http://:8999 -forward "tls://user:password@nl.secureconnect.me:7070" --verbose
2023/11/28 19:32:25 group.go:191: [group] main: only 1 forwarder found, disable health checking
2023/11/28 19:32:25 server.go:30: [http] listening TCP on :8999
2023/11/28 19:32:56 server.go:96: [http] 127.0.0.1:33144 <-> www.google.com:443 [c] via nl.secureconnect.me:7070
2023/11/28 19:32:57 server.go:99: [http] 127.0.0.1:33144 <-> www.google.com:443 via nl.secureconnect.me:7070, relay error: read tcp 127.0.0.1:8999->127.0.0.1:33144: read: connection reset by peer
2023/11/28 19:32:57 server.go:162: [http] 127.0.0.1:33146 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:32:58 server.go:162: [http] 127.0.0.1:33152 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:32:59 server.go:162: [http] 127.0.0.1:33154 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:32:59 server.go:162: [http] 127.0.0.1:33170 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:33:00 server.go:162: [http] 127.0.0.1:33178 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:33:01 server.go:162: [http] 127.0.0.1:33188 <-> detectportal.firefox.com:80 via nl.secureconnect.me:7070
2023/11/28 19:33:01 server.go:54: [http] can not parse request from 127.0.0.1:33134, error: EOF

And also

./gliderlisten http://:8999 -forward "http://user:password@nl.secureconnect.me:7070" --verbose 
2023/11/28 19:42:13 group.go:191: [group] main: only 1 forwarder found, disable health checking
2023/11/28 19:42:13 server.go:30: [http] listening TCP on :8999
2023/11/28 19:42:22 server.go:89: [http] 127.0.0.1:47200 <-> www.google.com:443 [c] via nl.secureconnect.me:7070, error in dial: read tcp 192.168.31.153:56541->206.217.216.25:7070: read: connection reset by peer
danilovsergei commented 1 year ago

It looks like I find out. https proxy configuration with user password looks like this:

./glider -listen http://:8999 -forward "tls://mx.secureconnect.me:7070,http://user:password@"

Examples have that line, but there is no explanation what it does. It looks quite technical to understand what tls://mx.secureconnect.me:7070,http://user:password@ does

Maybe it makes sense to add to README simple explanation to use that line for https with user/pass ?

github-actions[bot] commented 7 months ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.