I run a Discourse site and I wish to start by saying how much I love this software. Thanks to all the team for the great work, this is an awesome tool. After a 2.5.0 upgrade, I went into big troubles. Here is the recap and the workaround I did. Maybe this will lead to a much better fix in future ve…

Thanks @david , I confirm a fresh rebuild against tests-passed worked out of the box. Thanks! Any suggestion on a proper/easy way to get rid of those dead links in topics?

We got the opposite behavior : logged in user is good, not logged in are unable to connect and get a error 500

[immagine] sukria: all logged-in users got 500 errors Can you share one full backtrace of such error? Check your /logs page.

[immagine] sukria: all logged-in users got 500 errors This to me very much sounds like an incompatible plugin, what unofficial plugins are you running? Have you tried rebuilding without them?

[immagine] Falco: Can you share one full backtrace of such error? Check your /logs page. Sure, in my log/production.log, I had the following exception (when Discourse was accessing the empty S3 bucket (which I recreated, hoping it would fix the problem). Started GET “/” for 86.246.127.170 …

[immagine] sam: This to me very much sounds like an incompatible plugin, what unofficial plugins are you running? Have you tried rebuilding without them? Thanks, that might be it. I indeed have two plugins installed: Discourse Adsense and discourse-chat-integration, I’ll try a rebuild without…

I can confirm this is not caused by a plugin : I reproduced the same bug with a fresh install + a restore of my last backup and no plugins installed unless docker_manager. The first stacktrace I get is : Completed 500 Internal Server Error in 4169ms (ActiveRecord: 0.0ms | Allocations: 72058) NoM…

Have you moved your files to or from s3 at some point in time?

Yes, I did. But then, the bucket got deleted. And I switched back to local storage (with dead image links in previous topics, obviously).

I think the best bet here is for you to hard nuke all the bad Upload rows from your database. If you have no upload, don’t keep it there.

Yes, I agree, but I’m afraid on running such a nuke by hand on the DB. Any suggestions for doing it “properly”? Or should I do it really “by hand” ? Also, I have the feeling this change of behavior from Discourse is a bit worrying. It means, as far as I can tell, that if at some point, there’s a de…

Link a caricamenti rotti nei topic causano errori 500 con 2.5.0

Supporto

ParrotDeveloper 18 Maggio 2020, 1:51pm 12

Molto simile a quello che abbiamo:

L’ho “risolto” rieseguendo la procedura guidata di configurazione!

Argomento		Risposte	Visualizzazioni
Upgrade broke images Support	4	901	Giugno 27, 2020
Broken Images and Their S3 URLs Support	33	4610	Settembre 30, 2020
Old image uploads become broken images Support	64	8630	Giugno 8, 2024
Migrate_to_S3 Fails on Rebake Self-hosting	17	2482	Settembre 10, 2022
Error 500 / not logged in Support	10	978	Maggio 19, 2020

Link a caricamenti rotti nei topic causano errori 500 con 2.5.0

Argomenti correlati