I'm using warp for a HTTP server. The server refuses to connect unless I use a proxy. I can access the server on the local machine just fine but on a separate machine (my phone), I get ERR_CONNECTION_FAILED. If I run the server through a proxy (armor), it works.
The code to start up the server is pretty standard.
warp::serve(routes.with(warp::log(""))) .run(([127, 0, 0, 1], 3030)) .await;
I configured the proxy using this:
address: ":8080" plugins: - name: logger - name: proxy targets: - url: "http://localhost:3030"
Then I did
armor -c config.yaml.
I tried changing the port. I tried passing an IPv6 address to
run. In either case, localhost works but a separate machine requires a proxy. I don't know what armor is doing that warp isn't. My networking knowledge is pretty limited. I should also mention that nothing appears in the warp log when the connection fails. So I don't think it has anything to do with the filters because it doesn't seem to be reaching that point.