A user, pmichelu, encountered an “Invalid location error” after updating their Discourse instance, with a log error indicating a missing translation file. pfaffman suggested a rebuild using ./launcher rebuild app, which resolved the issue. pmichelu confirmed the fix worked after running the command twice and noted that the forum content remained intact. pfaffman added that the update involved a PostgreSQL 13 upgrade, which is a rare but necessary process requiring periodic command-line updates.
Hi! I just ran the automated update on our Discourse instance a few days ago (it’s in a docker container). Now it’s dead in the water - when you go to the site it shows the “Oops” message.
I used “tail shared/standalone/log/rails/production.log” to get the following log output:
Job exception: can not load translations from /var/www/discourse/config/locales/client.en_US.yml: #<Errno::ENOENT: No such file or directory @ rb_sysopen - /var/www/discourse/config/locales/client.en_US.yml>
This was a complicated upgrade that included a PostgreSQL 13 update. That kind of upgrade usually happens less than once a year. You’ll need to do a command line upgrade about 3 times a year.