A user, v.stephan, reports a 500 error when accessing the private messages inbox for one specific user on their self-hosted Discourse instance (v2.6.0.beta3), while other message routes work fine. The error occurs at /topics/private-messages/firstname.name.json and is tied to a NoMethodError: undefined method 'downcase' for nil:NilClass in global_setting.rb, specifically around s3_bucket_name, despite no S3 storage being configured. Community members, including RGJ, sam, Falco, and martin, suggest checking secure media settings, URL case sensitivity, and running rake uploads:secure_upload_analyse_and_update — though this fails as it requires external storage. Ed_S hypothesizes the issue stems from a corrupted or problematic profile image in the message list serialization, and suggests sending new messages to push the bad entry off the recent list — which successfully resolves the issue for v.stephan. The root cause remains unclear, but Ed_S recommends using the Data Explorer plugin to investigate further. The user expresses gratitude and seeks guidance on preventing recurrence or identifying the faulty image. No permanent fix is confirmed, but the workaround restores functionality.
We tried changing the roles of this user, we made updates, and rebuilt the app via the launcher. Unfortunately, it still results in a 500 error when opening the inbox.
Has anyone ever encountered such behavior? What can we do? Is there a way to rebuild the messages? Or do we have to delete them?
I saw something similar the other day, with a group name in /topics/private-messages-group. It turned out that there was a case sensitive search, and the group name in the URL was all in lowercase.
Can you check if this behaves differently if you change the case in the URL to match the case of the username? (so something like https://domain.de/u/Firstname.Name/messages)
I really hope some could help me with our problem. As far as @RGJ hints, we found out, that things seem to lie a bit deeper, but we could not solve the problem, of unreachable inboxes of a single user, yet. Unfortunately we really use messages a lot. We are kind of organized in small groups that often need to communicate not public. Therefor messages are a perfect way to got.
If you some more information, let me know or logging, tell me what and I will paste it here.
Thank you all for further hints and still for reading
Well this is a lot and I do not have a clue where to look in. I hope this can bring some light to our problem. If you need any further information, please let me know.
Thank you so much for taking a look into that!
THX
S3 Bucket Name seems to be something connected to the S3 Amsazon Storage Systems right? And if so, no probably it can’t be invalid. We never configured one. We are running dockerized discourse on a reverse proxy apache domain.
And should not crash a lot more if S3 Bucket is invalid, not just one route of one user?
Please, do not get me wrong. I might be on a total wrong path here. As I said, I am not that sure what this s3_bucket_name is or lets say – when I understood it right – why it should be configured.
Can I look it up in admin panel or do I need to check docker-compose?
Sorry for the time delay … different time zones and work hours … you know.
Is there still know one here, having any idea, what we could try?
Well, the thing ist, that we have this issue for one of our admins and it makes it pretty hard to communicate having one admin, thats not able to answer to messages or view them.
For the moment it would be a solution if the messages inbox would be reachable again. So is there any hack or possibility to rebuild one single user account or to – I don’t know – delete all messages for one single user? So that we could start from the scratch with this account?
Moreover I was even thinking about, deleting this account, but as far as I got it deleting users is not possible. What else could we try to start a new account for this user, that participating is possible again?
Please, let me know what Ideas you have, I am lost her.
Hi,
looks like I am facing a similar problem here. The messages for a single user, as far as we know, are not working.
Any further ideas, what we can have a look at??
I the meantime we thought around a bit. Maybe anyone else has some input to share.
An other strange thing is, the in the messeage pane area, by clinking on the user icon and the clicking the envelope. There should be displayed all recent messages, right? In the case of our users that is not able to open the inbox there is just nothing?
Maybe someone has some ideas on that. When we can for sure say that there sould be listed some entries.
And some other route of thinking. We still have some kind off ssl error on our site. As I said, running discourse with docker on a reverse proxy on apache. But the domain has its working ssl cert by lets encrypt.
Still we have some mixed content warnings on the site. By any means the standard logos and favicons are served by http. We deleted the custom brandings in behalf of getting rid of the mixed content errors.
So is there any chance that this might cause the problem?