# Sprites not reachable

**URL:** <https://community.fly.io/t/sprites-not-reachable/28855>\
**Category:** Questions / Help\
**Tags:** sprites\
**Created:** [October 17, 2026, 10:56pm UTC](https://community.fly.io/t/sprites-not-reachable/28855 "2026-10-17T22:56:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![siscia](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@siscia](https://community.fly.io/u/siscia)\
**Post date:** [October 17, 2026, 10:56pm UTC](https://community.fly.io/t/sprites-not-reachable/28855/1 "2026-10-17T22:56:20Z")

</div>

My sprite is not reachable.

It was running some workload and it is now completly unreachable.

The CLI nor the exposed web port seems to work.

sprite-4dd628e4-b4ab-43f4-be25-993d6beb66ea

---

<div class="post-metadata">

**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\
**Post date:** [October 17, 2026, 11:09pm UTC](https://community.fly.io/t/sprites-not-reachable/28855/2 "2026-10-17T23:09:47Z")

</div>

Hi… Do you see a `Restart` button in the dashboard?

> [@Can we please have a restart button for sprites?](https://community.fly.io/t/can-we-please-have-a-restart-button-for-sprites/27940/3):
>
> ![CleanShot 2026-05-26 at 13.41.23](https://global.discourse-cdn.com/fly1/original/3X/0/2/020741248f9940993b07298dc3207c28e40d3e8d.png)
> 
> It won’t solve every case of wedged sprites but it is something to try. It tries to do a graceful restart but if you have data on the sprite that is vital, I’d be cautious as I would with any restart.

(People have reported some success with that, in the past…)

---

<div class="post-metadata">

**Author:** ![siscia](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@siscia](https://community.fly.io/u/siscia)\
**Post date:** [October 17, 2026, 11:20pm UTC](https://community.fly.io/t/sprites-not-reachable/28855/3 "2026-10-17T23:20:20Z")

</div>

Thanks, eventually it become responsive from the CLI again. However, the service I used was stopped.

Which means that I had to log into the CLI, restart the service, and then I can start using it again - which is not quite the workflow I was looking for.

---

<div class="post-metadata">

**Author:** ![siscia](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@siscia](https://community.fly.io/u/siscia)\
**Post date:** [October 18, 2026, 4:11am UTC](https://community.fly.io/t/sprites-not-reachable/28855/4 "2026-10-18T04:11:45Z")

</div>

Nope… It happened again.

Is this expected?

---

<div class="post-metadata">

**Author:** ![flyio-support](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/flyio-support/32/46245_2.png) [@flyio-support](https://community.fly.io/u/flyio-support)\
**Post date:** [October 19, 2026, 7:57am UTC](https://community.fly.io/t/sprites-not-reachable/28855/6 "2026-10-19T07:57:45Z")

</div>

We’ve updated sprite-4dd628e4-b4ab-43f4-be25-993d6beb66ea. It’s now running and healthy.