More Fly Answers To Questions

Q: Is it ok to run non-HTTP apps on Fly? From Pier via community.fly.io A: It is, with one caveat: your applications need to have a network service of some kind. Why is that? Well, when your app deploys, we run health checks to ensure you can connec

Fly.io logo
Fly.io
•
Dj Walker-Morgan
•4 min read•beginner•
--
•View Original
HTTPSPrometheus

Overview

The article provides answers to frequently asked questions about Fly, a platform for deploying applications. It addresses topics such as running non-HTTP apps, IP ranges, app renaming, and community engagement.

What You'll Learn

1

How to run non-HTTP applications on Fly

2

Why IP ranges are complicated on Fly and how to manage security

3

How to rename an app on Fly with a workaround

Key Questions Answered

Is it ok to run non-HTTP apps on Fly?
Yes, you can run non-HTTP apps on Fly, but they must have a network service for health checks. Without a network service, health checks will fail, and Fly will terminate the app.
What IP ranges does Fly use?
Fly operates within AS40509, but IP addresses may change frequently due to the addition of new servers. It's recommended to use improved authentication methods for security.
How can I rename an app on Fly?
Currently, there is no direct way to rename an app on Fly. However, a workaround exists that involves creating a new app with the desired name, but this will result in the loss of the original app's history and configuration.

Key Actionable Insights

1
Ensure your non-HTTP applications have a network service to pass health checks on Fly.
This is crucial because without a network service, your app will be terminated by Fly, impacting your deployment.
2
Consider using client certificates during TLS connections for enhanced security with Fly's dynamic IP addresses.
This approach mitigates risks associated with changing IP addresses and helps secure your connections.
3
Utilize the Fly Community for support and to share experiences with other users.
Engaging with the community can provide valuable insights and assistance, enhancing your overall experience with Fly.

Common Pitfalls

1
Failing to configure a network service for non-HTTP apps can lead to unexpected app terminations.
This happens because Fly relies on health checks to determine app viability. Without a network service, the health checks will fail.