# Unable to view Logster

**URL:** https://meta.discourse.org/t/unable-to-view-logster/254017
**Category:** Support
**Created:** [February 4, 2023, 12:44am UTC](https://meta.discourse.org/t/unable-to-view-logster/254017 "2023-02-04T00:44:51Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mjr4684](https://avatars.discourse-cdn.com/v4/letter/m/49beb7/32.png) [@mjr4684](https://meta.discourse.org/u/mjr4684)
#### Post date: [February 4, 2023, 12:44am UTC](https://meta.discourse.org/t/unable-to-view-logster/254017/1 "2023-02-04T00:44:51Z")

</div>

I recently updated Discourse to 3.1.0.beta2 and it appears that Logster is no longer working. Checking the console reveals that GET requests to /logs/messages.json are now coming back with a 404 error. I remember seeing that Logster was updated to use POST instead of GET about 4 days ago, could this have anything to do with these console errors?

Prior to the update Logster was working without issue.

Thanks,  
Michael

---

<div class="post-metadata">

### Author: ![mjr4684](https://avatars.discourse-cdn.com/v4/letter/m/49beb7/32.png) [@mjr4684](https://meta.discourse.org/u/mjr4684)
#### Post date: [February 6, 2023, 4:06pm UTC](https://meta.discourse.org/t/unable-to-view-logster/254017/2 "2023-02-06T16:06:35Z")

</div>

Disregard, this is now working again as of build 84e13e9b1c

Thanks,  
Michael

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [March 8, 2023, 4:07pm UTC](https://meta.discourse.org/t/unable-to-view-logster/254017/3 "2023-03-08T16:07:12Z")

</div>

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