Closed luisorbaiceta closed 7 months ago
Even if I set the ConnectPort
to 0
I keep getting the same error
I have no idea how to handle that situation, sorry. I did find a lot of useful information here: https://github.com/tinyproxy/tinyproxy/issues/388. It seems tinyproxy doesn't support listening using HTTPS and you'd need something like stunnel in front of it as suggested. Makes sense as there isn't any configuration options for HTTPS server certificate in tinyproxy either.
If you manage to get something to work, I'll gladly include the relevant changes.
It would probably be simpler if render.com would allow controlling the redirection behavior though.
Message received from the render.com team
Hi,
Proxies are against our Acceptable Use Policy.
Kind regards
I have deployed to render.com just providing the docker registry url and adding de ALLOWED_NETWORKS environment variable but tinyproxy is not working as expected.
By default Render detects the exposed port (8888).
Problem seems to be that Render automatically redirects requests to a secure connection (443) which routes to the desired port. This results in a
curl: (56) CONNECT tunnel failed, response 400
Am I missing something with the configuration? Has anyone tried this in some service before and got it working? A guide on how to deploy to a hosting service would be awesome and if I solve this I'm willing to take the lead on that.
To reproduce
curl -x https://app-name.onrender.com https://google.com
Error