Hello! One thing that tripped me up that might also be a problem for you: Is the port listed in your fly.toml the same one as your app is listening on?
I encountered the same issue. Indeed the port was wrong in fly.toml, but this file was auto-generated the first time I ran flyctl launch, so I think there is something you should fix somewhere (I just generated the remix app, did changed anything, and executed flyctl launch, it should know remix is using port 3000 by default and not 8080).
Thanks for the reports. I’ve been trying to reproduce this with a fresh remix app, but haven’t been able to so far. Which version of flyctl are you using?
So the port mapping should be correct since fly.toml sets both the PORT environment variable, and the internal_port setting. One issue here may be that Remix is not using the PORT variable and listening on 3000 instead of 8080. In my tests with a fresh app, Remix listens on port 8080.