I need help because I have systems down and when I ssh into my proxy service, I get this message
curl http://[app-name].flycast:8080 -v
Host [app-name].flycast:8080 was resolved.
IPv6: [ipv6-addr]
IPv4: (none)
Trying [ipv6-addr]:8080…
Established connection to [app-name].flycast ([flycast-ipv6] port 8080) from [proxy-ipv6] port [ephemeral-port]
using HTTP/1.x
GET / HTTP/1.1
Host: [app-name].flycast:8080
User-Agent: curl/8.17.0
Accept: */*
Request completely sent off
Recv failure: Connection reset by peer
closing connection #0
curl: (56) Recv failure: Connection reset by peer
Hi… Typically, you would leave the :8080 off the .flycast address, since that’s the internal port. The Fly Proxy is usually listening on port 80 instead.
If that doesn’t work, post your full fly.toml, and people might be able to give further tips. You can use the </> button in the toolbar to get an area suitable for pasting code.
Right, but if I specify the internal port in the fly file, and specify it in the http routing, should it not resolve to the correct path. Additionally you can see in the logs flycast making the connection and resolving the ip, then having the connection reset by peer, maybe indicating some kind of connection problem
It listens on ports that typically aren’t the same as the internal_port in fly.toml.
You can see the mapping in the output of fly services list, if you prefer to post that instead. We forum readers generally can’t poke around in your app settings, etc.
The Fly Proxy always does that when it doesn’t recognize the port of an incoming connection.
Ah, I was misunderstanding the connection, I knew about the internal flycast proxy, but mixed up the connecting internal_port is different than just the general connection to the flycast proxy.
Thank you for clarifying! I just tested it internally and seems to be working thanks!