attempting to login into a ai assistant gives me error 500

Thank you for contacting JetBrains Support, and I apologize you’re running into this — a 500 during login is especially annoying because it blocks you completely, and reinstalling usually won’t help if the failure is happening server-side.

From the error text, the IDE successfully reaches the JetBrains AI auth endpoint, but the backend returns HTTP 500 Internal Server Error during the registration step:

• `https://api.jetbrains.ai/auth/jetbrains-jwt/register` → 500
and it chains to
• `https://auth.grazie.ai/auth/jetbrains-jwt/register` → 500
• with request/error id: `b5ceb74a59b2511f9bdc513ae913fb68`

That pattern usually means the client is not the primary culprit (so restarting the IDE / reinstalling won’t reliably fix it). However, there are still a few local/environment items that can trigger or amplify server failures (proxies/SSL interception, wrong system time, etc.).

The following steps usually resolve the issue:

1. Things to check locally (quick and safe)

• System date/time: ensure macOS time/date/timezone are correct (JWT-based auth is sensitive to clock skew).
• Network path:
    • If you have a VPN, corporate network, or secure DNS, try temporarily disabling them.
    • If you’re on a corporate network, try a different network (e.g., mobile hotspot) to rule out proxy/inspection.
• Proxy settings in IDE: Settings/Preferences → search “Proxy”
    • If set to manual, verify it’s correct.
    • If you’re behind a proxy that performs TLS inspection, it can break auth flows in ways that surface as server errors.

2. Capture the exact diagnostic data JetBrains will need
Since this is a 500 with a request id, the backend team can usually find the failure quickly if the id is provided.

Please collect:

• The error id you already have: `b5ceb74a59b2511f9bdc513ae913fb68`
• The exact IDE version/build (you already have this in your earlier system info; include it again with the auth issue)
• IDE logs from the moment you click “Sign in”:
    • Help → Collect Logs and Diagnostic Data
    • Attach the resulting archive to the YouTrack issue or support thread

3. Use the existing YouTrack issue (best path)
Since you already found LLM-22228, the most effective action is to add a comment there with:

• the error id `b5ceb74a59b2511f9bdc513ae913fb68`
• your IDE build number
• whether it reproduces on a different network (yes/no)
• the collected logs archive (if possible)

That gives the team what they need to correlate your failure with backend logs and confirm whether it’s the same root cause as LLM-22228 or a separate incident.

Kind regards,

Emin.

Hi Elhanan. 

Thank you for reaching out with the follow-up and the additional information.

Unfortunately, this error can be caused by multiple underlying issues, and it’s not possible to determine the exact root cause without additional diagnostic information. To proceed with the investigation, please submit a support ticket using the following form: https://intellij-support.jetbrains.com/hc/en-us/requests/new?ticket_form_id=66731&product=ai_assistant
If the issue persists, we kindly ask you to include the AI Assistant troubleshooting logs with your ticket. Ideally, please enable HTTP request logging, as this will significantly help us identify the cause of the problem.
You can find step-by-step instructions on how to enable, collect, and upload the logs in the following article: https://youtrack.jetbrains.com/articles/SUPPORT-A-75/How-to-collect-IntelliJ-IDEA-logs-to-troubleshoot-AI-Assistant-issues

Once we have the logs, we’ll be happy to continue the investigation.

Best regards,
Oleg