[GH-ISSUE #1555] Deleted a file while running #1094

Closed
opened 2026-05-07 00:30:13 +02:00 by BreizhHardware · 9 comments

Originally created by @covercanvas on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1555

I used the latest ntfy executable, ran it directly on an armhf device, and then forcibly deleted the file using the rm command while it was running. However, the page on port 80 of my device still exists, and I cannot find it using commands like netstat or ps.

Originally created by @covercanvas on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1555 I used the latest ntfy executable, ran it directly on an armhf device, and then forcibly deleted the file using the rm command while it was running. However, the page on port 80 of my device still exists, and I cannot find it using commands like netstat or ps.
BreizhHardware 2026-05-07 00:30:13 +02:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@covercanvas commented on GitHub (Jan 18, 2026):

Where are the files related to the web server located?

<!-- gh-comment-id:3765459700 --> @covercanvas commented on GitHub (Jan 18, 2026): Where are the files related to the web server located?
Author
Owner

@wunter8 commented on GitHub (Jan 18, 2026):

The web app files are all bundled inside the ntfy binary

<!-- gh-comment-id:3765468032 --> @wunter8 commented on GitHub (Jan 18, 2026): The web app files are all bundled inside the ntfy binary
Author
Owner

@wunter8 commented on GitHub (Jan 18, 2026):

It's possible your browser cached the web app files, so you're seeing the web app even though the backend isn't running anymore

<!-- gh-comment-id:3765469133 --> @wunter8 commented on GitHub (Jan 18, 2026): It's possible your browser cached the web app files, so you're seeing the web app even though the backend isn't running anymore
Author
Owner

@covercanvas commented on GitHub (Jan 19, 2026):

It's not a cache. After I forcibly deleted the running ntfy executable using rm, the 80 port was still responding with an HTTP 200 OK. I searched everywhere and couldn't find the possible file location.> It's possible your browser cached the web app files, so you're seeing the web app even though the backend isn't running anymore

<!-- gh-comment-id:3767963730 --> @covercanvas commented on GitHub (Jan 19, 2026): It's not a cache. After I forcibly deleted the running ntfy executable using rm, the 80 port was still responding with an HTTP 200 OK. I searched everywhere and couldn't find the possible file location.> It's possible your browser cached the web app files, so you're seeing the web app even though the backend isn't running anymore
Author
Owner

@wunter8 commented on GitHub (Jan 19, 2026):

Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in ps still. In any case, a restart would clear the memory

<!-- gh-comment-id:3768535239 --> @wunter8 commented on GitHub (Jan 19, 2026): Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in `ps` still. In any case, a restart would clear the memory
Author
Owner

@covercanvas commented on GitHub (Jan 19, 2026):

Of course, I have restarted many times and used various commands to search, but I still can't find it, and it doesn't even show the 80 port listening status.> Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in ps still. In any case, a restart would clear the memory

<!-- gh-comment-id:3769627740 --> @covercanvas commented on GitHub (Jan 19, 2026): Of course, I have restarted many times and used various commands to search, but I still can't find it, and it doesn't even show the 80 port listening status.> Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in `ps` still. In any case, a restart would clear the memory
Author
Owner

@covercanvas commented on GitHub (Jan 19, 2026):

Currently, the ntfy web interface only appears when accessing localhost; it does not show up when using the LAN IP or 127.0.0.1.> Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in ps still. In any case, a restart would clear the memory

<!-- gh-comment-id:3769633770 --> @covercanvas commented on GitHub (Jan 19, 2026): Currently, the ntfy web interface only appears when accessing localhost; it does not show up when using the LAN IP or 127.0.0.1.> Hmm. Have you tried restarting the device? I could imagine the executable existing and continuing to run in memory, though I would expect it to show up in `ps` still. In any case, a restart would clear the memory
Author
Owner

@wunter8 commented on GitHub (Jan 19, 2026):

What's the output of curl -v http://127.0.0.1:80? And curl -v http://localhost:80?

<!-- gh-comment-id:3769635334 --> @wunter8 commented on GitHub (Jan 19, 2026): What's the output of `curl -v http://127.0.0.1:80`? And `curl -v http://localhost:80`?
Author
Owner

@wunter8 commented on GitHub (Jan 19, 2026):

Currently, the ntfy web interface only appears when accessing localhost; it does not show up when using the LAN IP or 127.0.0.1.

That sounds like a browser cache issue. If you first accessed the web app at http://localhost and not at http://127.0.0.1, then the files would be cached in one spot but not the other

<!-- gh-comment-id:3769638024 --> @wunter8 commented on GitHub (Jan 19, 2026): > Currently, the ntfy web interface only appears when accessing localhost; it does not show up when using the LAN IP or 127.0.0.1. That sounds like a browser cache issue. If you first accessed the web app at http://localhost and not at http://127.0.0.1, then the files would be cached in one spot but not the other
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#1094
No description provided.