We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While attempting to migrate discourse.specifiction.org into discuss.webplatform.org (ref #152) images of avatars are broken.
Note we didn’t setup asset storage on S3.
Internal communication between frontend NGINX server didn’t pass proxy_set_header X-Forwarded-Proto https;? (outcome, it didn’t change anything)
proxy_set_header X-Forwarded-Proto https;
Run recommended steps (outcome; read and tried this, this and this , didn’t change anything)
./launcher enter app rake posts:rebake rake uploads:clean_up
Migrated from specifiction.org to webplatform.org from backup generated from the same Discourse version on both installs? (needs investigation 👍 )
The text was updated successfully, but these errors were encountered:
Solution, re-import backup from original that has the same version as new deployment, plus;
NOTE: didn´t test without it, it was just in case.
Sorry, something went wrong.
Solved!! \o/
Sent in "Work status update" email on devrel list
renoirb
No branches or pull requests
While attempting to migrate discourse.specifiction.org into discuss.webplatform.org (ref #152) images of avatars are broken.
Possible causes
Note we didn’t setup asset storage on S3.
Internal communication between frontend NGINX server didn’t pass
proxy_set_header X-Forwarded-Proto https;
? (outcome, it didn’t change anything)Run recommended steps (outcome; read and tried this, this and this , didn’t change anything)
Migrated from specifiction.org to webplatform.org from backup generated from the same Discourse version on both installs? (
needs investigation👍 )How it looks like
The text was updated successfully, but these errors were encountered: