502 Bad Gateway error on loading assets #86212
Labels
No Label
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Websites
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-cloud#86212
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For example, when visiting https://cloud.blender.org/p/characters/ as logged in user, all static assets return the error. Unauthenticated users don't see this issue.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @fsiddi
It looks like the same 50X that was reported a few times in #blender-web-dev , and is probably caused by a request to Blender ID timing out (this issue is 3 years old): https://sentry.io/organizations/blender-institute/issues/419095813/?project=256024&query=is%3Aunresolved+timeout&statsPeriod=14d
Since it's not reproducible, it seems to depend on the traffic to Blender ID, so a good start would be to stop trying to validate Blender ID tokens on each request to static web assets, which show up in the list of URLs this error happened at:
Can assets under
/static/pillar/assets/*
and/static/cloud/assets/*
be served by the webserver instead of Pillar?Or, if not, is there a way to tell web assets from assets for which authentication is actually needed?
Thanks for looking into this.
/static
used to be served through the webserver because also actual cloud assets were served from it.Since now everything has been moved to buckets, it should be indeed possible to serve
/static
straight from Apache.