# Is there a way to block requests before they reach my Fly.io app?

**URL:** <https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350>\
**Category:** Questions / Help\
**Tags:** wishlist, machines, proxy\
**Created:** [July 23, 2026, 1:48pm UTC](https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350 "2026-07-23T13:48:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![veselidrago](https://avatars.discourse-cdn.com/v4/letter/v/f04885/32.png) [@veselidrago](https://community.fly.io/u/veselidrago)\
**Post date:** [July 23, 2026, 1:48pm UTC](https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350/1 "2026-07-23T13:48:09Z")

</div>

Hi everyone,

I was previously using Cloudflare Security Rules to allow only specific requests to reach my [Fly.io](http://Fly.io) application. Unfortunately, that approach no longer works for my use case.

My goal is to stop unwanted requests **before they reach my [Fly.io](http://Fly.io) instance**, so they don’t consume application resources or appear in my application logs.

Is there any Fly.io-native solution for this? For example:

- Filtering requests at the Fly Proxy level
- IP allowlists/blocklists
- Path-based filtering
- Custom rules that can reject requests before they’re forwarded to the application
- Any other built-in mechanism

I’m aware I could implement filtering inside my application or with a reverse proxy, but I’m specifically looking for a solution that blocks requests before they ever reach the instance.

Has anyone solved this problem, or is this something [Fly.io](http://Fly.io) currently doesn’t support?

Thanks!

---

<div class="post-metadata">

**Author:** ![khuezy](https://avatars.discourse-cdn.com/v4/letter/k/4da419/32.png) [@khuezy](https://community.fly.io/u/khuezy)\
**Post date:** [July 24, 2026, 1:32pm UTC](https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350/3 "2026-07-24T13:32:49Z")

</div>

From my knowledge, fly doesn’t support any of that.

You’ll have to create a reverse proxy and handle everything yourself unfortunately.

---

<div class="post-metadata">

**Author:** ![halfer](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@halfer](https://community.fly.io/u/halfer)\
**Post date:** [August 1, 2026, 6:50pm UTC](https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350/4 "2026-08-01T18:50:33Z")

</div>

> [@veselidrago](#):
>
> I was previously using Cloudflare Security Rules to allow only specific requests to reach my [Fly.io](http://Fly.io) application. Unfortunately, that approach no longer works for my use case.

Would you explain why? Maybe someone can speak to your reasoning that would permit Cloudflare to still work for you.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [August 11, 2026, 6:50pm UTC](https://community.fly.io/t/is-there-a-way-to-block-requests-before-they-reach-my-fly-io-app/28350/5 "2026-08-11T18:50:38Z")

</div>

Closed on August 11, 2026, 6:50pm UTC

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
