Dockerfile works locally but is crashing on Railway
This works when I run locally. When I run online I am getting the following error in stdout. changed url with xxxx:xxxx
What seems to be the issue?
17 Replies
Project ID:
N/A
N/A
the
xxxx:xxxx
is kinda (very) important debugging informationsadly I deleted the project already.
But replication is straight forward. Just run that Dockerfile.
Port=8080 key=anything
and then do to the domain:8080 TCP tunneling.
okay then would
xxxx:xxxx
have been an internal or public address and port?Yes.
external one.
Hi @Brody did you get a chance to test this?
I haven't sorry, will try to test today
would it be hard for me to obtain a zap api key?
i wasn’t able to reproduce the
ZAP Error [org.apache.hc.core5.http.NoHttpResponseException]: xxxx:xxxx failed to respond
error.
i deployed the softwaresecurityproject/zap-stable
image with a start command set to /bin/sh -c "zap.sh -daemon -host [::] -port $PORT"
opened the public url and was greeted with ERR_TOO_MANY_REDIRECTS
Did you do TCP tunneling? @Brody
and not visit the given URL directly.
is this not an http service?
i mean it says
Http
in your errorIt is. But it is mainly run on local servers or cloud VMs, on the IP. I figured you should use the TCP tunneling in order to make it work
then you dont get any ssl cert
Yes. SSL cert not needed.
still, its an http service, it doesn't make sense to use the tcp proxy
For now even if we use TCP proxy it throws this error.
use the https domain and let me know if you are able to configure zap to stop sending the redirects
I don't think that will work. I faced the same issue earlier.
yeah it's not gonna work if zap keeps sending the redirects for whatever reason