Mixamo down issue

Guys I inspected the website and I found a few errors and then I gave those to AI and asked to address the issue and I would like to share the response here. This is not a solution or anything; it is just an understanding of the issue:

You've provided some excellent insight into the problem by inspecting the Mixamo website\! These console errors clarify what's happening beyond just a generic "Too Many Requests" message. Let's break them down:

Understanding the Errors

You're seeing two main types of errors:

1. "Refused to load the script 'blob:\<URL\>' because it violates the following Content Security Policy directive..."

Content Security Policy (CSP): This is a security feature implemented by websites to prevent Cross-Site Scripting (XSS) attacks and other forms of code injection. It works by telling the browser exactly which sources are allowed to load scripts, styles, images, etc. If a resource tries to load from a source not explicitly listed in the CSP, the browser blocks it.
`script-src` directive:** This specific part of the CSP dictates where JavaScript code is allowed to load from.
`blob:<URL>`: A "blob" URL (Binary Large Object) is a pseudo-URL that refers to data stored in the browser's memory, often generated dynamically by JavaScript. It's frequently used for things like creating temporary files, displaying generated content, or handling large binary data.
The Violation: The error message clearly states that Mixamo's CSP (`script-src https://.adobe.com ... 'unsafe-inline' 'unsafe-eval' 'self'`) does not include `blob:` as an allowed source for scripts. This means that when Mixamo's own JavaScript tries to generate and execute a script from a `blob:` URL (which it likely does for some internal functionality, perhaps related to processing models or animations in your browser), the browser, following Mixamo's security policy, blocks it.
Why is this a problem? If Mixamo's internal code relies on executing scripts from blob URLs, and their CSP prevents this, then core functionality will break. This isn't something you can fix as a user; it's a misconfiguration on Mixamo's server/development side. They would need to update their CSP to explicitly allow `blob:` for `script-src` (e.g., `script-src ... blob: ...`) if that's indeed how their application is designed to function. However, allowing `blob:` in `script-src` can sometimes weaken security, so it needs to be done carefully.

2. "Failed to load resource: the server responded with a status of 500 (Internal Server Error)"

HTTP 500 Internal Server Error: This is a generic server-side error. It means that the server encountered an unexpected condition that prevented it from fulfilling your request. Unlike 4xx errors (like 429), which are client-side errors (meaning your request was somehow incorrect or exceeded limits), a 500 error means the problem is on Mixamo's end.
Specific Endpoints: You're seeing this for `/api/v1/characters/update_primary` and `/api/v1/animations/export`.
`/api/v1/characters/update_primary`: This likely relates to updating your selected character, perhaps when you upload a new one or switch between them.
`/api/v1/animations/export`: This is directly related to downloading or processing animations.
What it implies: These 500 errors indicate that the server's backend processes are failing when trying to handle these specific requests. This could be due to:
Server Overload: Too many users hitting the service at once, exhausting server resources.
Bugs in Mixamo's Code: An unhandled exception or bug in the server-side application logic.
Database Issues: Problems connecting to or querying their database.
Misconfiguration: Incorrect server settings or file permissions.
The CSP issue might be a symptom of a larger problem: It's possible the CSP issue is *related* to what's causing the 500 errors. For example, if the blocked `blob:` scripts are critical for preparing data on the client-side before sending it to the server for processing, then blocking them could lead to malformed requests that the server can't handle, resulting in a 500.

3. "Failed to load resource: the server responded with a status of 429 (Too Many Requests)"

This is the error you initially mentioned. While the 500s are clear server-side failures, and the CSP indicates a potential misconfiguration, the 429 means you've hit their rate limit.
Interplay: It's possible that the initial server errors (500s) lead to the client-side (your browser) retrying the requests multiple times in quick succession, which then triggers the 429 "Too Many Requests" error. So, the 429 might be a consequence of the underlying 500 errors and/or the CSP issues, rather than the primary cause of your problem.

Conclusion

Based on these errors, especially the repeated 500 Internal Server Errors and the Content Security Policy violations for `blob:` scripts, it's definitively a problem on Mixamo's side.

CSP Violation: This is a critical security configuration issue that only the Mixamo development team can address by updating their `Content-Security-Policy` header.
500 Internal Server Errors: These are direct indicators of server-side failures during processing your requests, again, something only Mixamo's engineers can investigate and fix.
429 Too Many Requests: While this indicates you're sending too many requests, it's highly probable that your browser is doing so because the preceding requests (which were failing with 500s or CSP violations) weren't successful, leading to retries that hit the rate limit.

What you should do:

Continue to follow the advice from the previous response:

Wait: This is still the most practical advice for end-users when encountering widespread server-side issues. Adobe is likely aware and working on it.
Check Adobe/Mixamo Community Forums: Look for official announcements or other users reporting these specific errors. This will confirm it's not isolated to you.
Report the specific errors to Adobe/Mixamo Support: If you have time, provide them with these detailed console logs. This helps them diagnose the problem more quickly. Screenshots of the console errors are particularly useful.

Unfortunately, there's nothing you can do on your end to resolve these specific errors, as they point to fundamental issues with Mixamo's website configuration and server health.