# Inbox gebruikersberichten Fout 500

**URL:** <https://meta.discourse.org/t/user-messages-inbox-error-500/165937>\
**Category:** Self-hosting\
**Created:** [1 oktober 2020 om 15:27 UTC](https://meta.discourse.org/t/user-messages-inbox-error-500/165937 "2020-10-01T15:27:38Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [20 oktober 2020 om 20:24 UTC](https://meta.discourse.org/t/user-messages-inbox-error-500/165937/31 "2020-10-20T20:24:37Z")

</div>

Ha ha - seems like I got lucky. The thing about a stack trace is that it runs from the specific to the general - it’s not just a list of things, but a picture of the nested interactions from general code down to the specific machinery. So, the ‘image’ idea seemed interesting, because there are only profile images in the message list. And I think we’ve seen odd issues with profile images before.

But I have no idea why the code is looking at secure storage, if you’ve never used it.

I suspect a database query could list the images which would be fetched in this case, but I don’t know how you might find the rogue profile. If indeed, this is the story behind the stack trace.

---

_[View the full topic](https://meta.discourse.org/t/user-messages-inbox-error-500/165937)._
