Navigating Gemini Pro Errors (13) in Google Workspace: Admin Settings and Your www https workspace google com dashboard

Student encountering Gemini Pro
Student encountering Gemini Pro "Something Went Wrong (13)" error.

Unlocking Gemini Pro: Navigating "Something Went Wrong (13)" in Google Workspace

Are you encountering the frustrating "Something Went Wrong (13)" error when trying to use Gemini Pro, even while Gemini Fast and Gemini Thinking work perfectly? This specific issue often points to a deeper administrative or permission-related block within your Google Workspace environment. For many users, especially those leveraging institutional accounts like college emails, understanding your Workspace administrator's settings is key to resolving this.

The Challenge: Gemini Pro Access Blocked

A recent thread on the Google support forum highlighted this exact problem. A user, utilizing a college email, found their Gemini Pro access consistently blocked by the "Something Went Wrong (13)" error. Despite clearing browser cache and cookies, and even attempting Incognito mode, the issue persisted. A notable symptom was the absence of a 'Help' button on the Gemini interface, hinting at customized or restricted access, a common practice in educational or corporate Google Workspace setups.

Why "Something Went Wrong (13)"? The Workspace Admin Connection

As expert Fred SR pointed out in the forum, Error 13, particularly when other Gemini tiers function normally, strongly suggests a backend communication block or a permission issue tied to specific model access. This is almost always related to how your organization's Google Workspace administrator has configured access for different services and user groups. Just as administrators manage critical aspects like google storage usage and google disk usage for their users, they also control which AI features and services are available.

The missing 'Help' button further reinforces this. Google Workspace administrators often customize the user interface and restrict certain features, including support options, to streamline their support processes or enforce policies. This means that your access to Gemini Pro, and even the visibility of certain UI elements, is directly governed by your institution's settings, typically managed from the www https workspace google com dashboard.

Troubleshooting Steps for Gemini Pro Access

If you're facing this error, here’s a comprehensive approach, building on the advice from the support thread:

  • Try a Different Browser or Device: The first step is to rule out local browser-specific conflicts. As the original poster discovered, simply switching to an entirely different browser (e.g., from Chrome to Edge or Firefox) or device (like a smartphone or another computer) can sometimes resolve the issue by bypassing a deep-seated software conflict or a corrupted browser profile.
  • Disable VPNs, Ad-blockers, and Firewalls: These tools, while useful for privacy and security, can sometimes interfere with the connection to specific server endpoints required by advanced Google services like Gemini Pro. Temporarily disabling them can help diagnose if they are the root cause.
  • Contact Your Google Workspace Administrator (College IT Helpdesk): This is often the most crucial step for institutional accounts. Your college's IT department or Google Workspace administrator can:
    • Verify if Gemini Pro access is fully enabled and unrestricted for your student or staff group.
    • Check for any recent changes in Workspace permissions that might have inadvertently affected AI service access.
    • Confirm that your account isn't subject to any specific policies that limit access to advanced AI models.

    They manage the entire Workspace environment, including settings you'd find on the www https workspace google com dashboard, and are best equipped to confirm your permissions.

  • Submit Feedback to Google: If your IT department confirms everything is clear on their end and the issue persists across different browsers/devices, it's time to report a structured bug to Google's engineering team.

    You can typically do this via the Gemini interface (if you can find the option) or through general Google feedback channels. When submitting, be explicit:

    Receiving Error 13 on Gemini Pro. Gemini Fast and Thinking work normally. Cache cleared, Incognito tested. Using an EDU Workspace account.

    Include a screenshot of the error message if possible.

The Resolution: A Simple Browser Switch

In the original forum thread, the user successfully resolved their "Something Went Wrong (13)" error by simply switching to a different browser. While this points to a local browser issue in that specific case, it doesn't negate the strong possibility of Workspace administrative restrictions for others. It highlights the layered nature of troubleshooting such errors.

Key Takeaway for Workspace Users

For Google Workspace users, especially those in educational or corporate environments, persistent errors with advanced features like Gemini Pro often trace back to administrative permissions. Understanding that your access is governed by your organization's IT policies, managed via the www https workspace google com dashboard, is vital. Always start with local checks, but be prepared to engage your Workspace administrator for a definitive resolution.

Google Workspace admin dashboard showing AI and storage settings.
Google Workspace admin dashboard showing AI and storage settings.
GmailGoogle Chat

|

 Sign Up for Free TrialRequires Google Workspace Admin Permission
Live Demo
Communication performance dashboard