-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not connect #70
Comments
cat -n proxy.conf cat -n caddy.conf If I put the ports on the inside, Caddy will not start. Logs look like this: 2020/02/06 12:27:19 192.168.40.190 - - [06/Feb/2020:12:27:19 -0500] "CONNECT / HTTP/1.1" 502 16 caddy -plugins | grep forward caddy -version The 502's are dns failures; adblocking.. HTH |
1. Is bug reproducible with latest
forwardproxy
build?Yes
2. What are you trying to do?
Trying to connect the proxy
3. What is your entire Caddyfile?
4. How is your client configured?
5. How did you run Caddy? (give the full command and describe the execution environment). If multiple servers are used (for example with
upstream
), describe those as well.Under CentOS 7
caddy -conf Caddyfile
6. Please paste any relevant HTTP request(s) here.
7. What did you expect to see?
The proxy working on all three ports.
8. What did you see instead (give full error messages and/or log)?
When I try on port 80, it gave me "404 Site google.com is not served on this interface" on Firefox and "ERR_TUNNEL_CONNECTION_FAILED" on Chrome
On port 443, it gave me "Connection Reset" on Firefox and "ERR_EMPTY_RESPONSE" on Chrome
On port 11001, it gave me "Connection Reset" on Firefox and "ERR_PROXY_CONNECTION_FAILED" on Chrome
9. How can someone who is starting from scratch reproduce the bug as minimally as possible?
The text was updated successfully, but these errors were encountered: