Posts Unreadable After Backup Restoration - 500 Error Persists

Support
1

Hi everyone,

I’m facing a critical issue with my Discourse community and would really appreciate any help or advice you can provide. When trying to access any post, I see the error message: “Sorry, we couldn’t load that topic. This may be due to a connection issue. Please retry or contact us if the problem persists.” :sob: :sob:

In the browser’s developer console, I also get a 500 error with the following response: Failed to load resource: the server responded with a status of 500 () {"status":500,"error":"Internal Server Error"}. An example of an affected URL is: https://starorigin.net/t/topic/352/1.

Here’s what I’ve tried so far: I reinstalled Discourse from scratch, and the new community worked perfectly without any issues. However, after restoring my backup, the homepage loads fine, but every single post returns a 500 error when accessed. I also tried migrating to a new server, but the problem persists after restoring the backup.

I suspect that my backups might be corrupted, but I’m not entirely sure. To test this, I restored three different backups (from January 25, January 23, and January 6), and all of them resulted in the same 500 error after restoration. This is very confusing, as I don’t know what could have caused this issue across multiple backups.

Has anyone encountered a similar issue after restoring a backup? I’m currently stuck and unable to restore my community to full functionality, so any guidance or suggestions would be greatly appreciated. Thank you in advance for your help! :sob:

2

I tried creating a new post, but after publishing it, the new post also failed to open and displayed the same error. :sob:

3

Do you have any plugins installed?

Do you have the same plugins installed on the new system that you did on the one that made the backup?

4

Yes, the plugins should be the same. I copied the app.yml file from the old server to the new one, so the configurations are identical.

5

I have pinpointed the issue, and it is the AI plugin that is causing this problem.

1 Like
6

Right. I think I’d mostly figured that out for someone else yesterday but didn’t get far enough to know it was a bug