Skip to content
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

no route to host when trying to connect to same sever from inside ssl-proxy #9

Open
worksasintended opened this issue Mar 11, 2018 · 1 comment

Comments

@worksasintended
Copy link

worksasintended commented Mar 11, 2018

Hi there,
I am having the following issue: The proxy works fine to me. I use it to connect to a locally running nextcloud docker, but when I try to connect to the very same server (lets call him myurl.com) i can ping but not connect on https or https.
The parameters with which is start the container:
ssl-proxy:
image: justsml/ssl-proxy:latest
environment:
- HTTPS_PORT=8080
- SERVER_NAME=myurl.com
- UPSTREAM_TARGET=app:80
- CERT_PUBLIC_PATH=/certs/fullchain.pem
- CERT_PRIVATE_PATH=/certs/privkey.pem
- SSLProxyVerify=none
- SSLProxyCheckPeerCN=off
- SSLProxyCheckPeerName=off
- SSLProxyCheckPeerExpire=off
volumes:
- /home/nextcloud/certs:/certs:ro
links:
- app
ports: ['8080:8080']

If I now try to for example curl myurl.com I get no route to host, although there are running services on 80 and many other ports I can connect to from everywhere else. Any suggestions how to fix that would be appreciated. Thank you!

@worksasintended
Copy link
Author

Correctly it does say host unreachable while the nextcloud ontainer gives no route to host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant