# 2026.7.3 (ESR) - Something POST /srv/se regularly, resulting in 404 errors

**URL:** <https://meta.discourse.org/t/2026-7-3-esr-something-post-srv-se-regularly-resulting-in-404-errors/413542>\
**Category:** Bug\
**Tags:** dev-install\
**Created:** [September 29, 2026, 9:52am UTC](https://meta.discourse.org/t/2026-7-3-esr-something-post-srv-se-regularly-resulting-in-404-errors/413542 "2026-09-29T09:52:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manut](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manut/32/485119_2.png) [@manut](https://meta.discourse.org/u/manut)\
**Post date:** [September 29, 2026, 9:52am UTC](https://meta.discourse.org/t/2026-7-3-esr-something-post-srv-se-regularly-resulting-in-404-errors/413542/1 "2026-09-29T09:52:31Z")

</div>

On a fresh dev container:

1. open “/logs”
2. on another tab, visit a few pages, change tabs
3. “/logs” get filled with `ActionController::RoutingError (No route matches [POST] "/srv/se")`

I tracked down the issue to `/frontend/discourse/app/services/human-activity-tracker.js`.

---

<div class="post-metadata">

**Author:** ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)\
**Post date:** [September 29, 2026, 1:42pm UTC](https://meta.discourse.org/t/2026-7-3-esr-something-post-srv-se-regularly-resulting-in-404-errors/413542/4 "2026-09-29T13:42:44Z")

</div>

I’m getting this fairly frequently on my dev instance too (not on ESR). It just logs in the browser console randomly. Weird.

---

<div class="post-metadata">

**Author:** ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)\
**Post date:** [September 29, 2026, 2:21pm UTC](https://meta.discourse.org/t/2026-7-3-esr-something-post-srv-se-regularly-resulting-in-404-errors/413542/5 "2026-09-29T14:21:49Z")

</div>

Thanks for letting us know.

I’ve informed the relevant team about this, though it might take a bit of time for a response here.