Troubleshooting Inconsistent Gemini Errors: Country Not Supported, Error 14, and 1060
Persistent Gemini Errors: Understanding and Reporting Inconsistent Service Disruptions
Users of Google Gemini may occasionally encounter frustrating and inconsistent errors that disrupt their workflow. A recent discussion in the Google support forums highlighted a common scenario where Gemini exhibited a range of issues, including 'This country isn't supported,' Error 14, Error 1060 (on the web version), and infinite loading without a response. These problems persisted across multiple accounts, devices, internet connections, and even VPN configurations, suggesting a deeper, systemic issue rather than a localized client-side problem.
Identifying the Problem: A Cascade of Errors
The reported issues were characterized by their intermittent and varied nature:
- "This country isn't supported": Appearing shortly after sending a prompt.
- Error 14: An alternative error code sometimes displayed instead of the country-related message.
- Infinite Loading: Gemini displaying the typing/loading indicator indefinitely.
- Error Transition: A prompt initially returning Error 14, then switching to "This country isn't supported" upon retrying.
- Error 1060 (Web Version): Specific to the Gemini website during the outage period.
Extensive troubleshooting by the affected user, including testing various Google accounts, Android devices, internet connections, VPN providers, and server locations (Germany, France, Netherlands, US), confirmed that the issue was not isolated to their specific setup. The fact that another user in the same geographical area experienced identical problems, and that Gemini briefly functioned normally during the outage before failing again, strongly indicated a broader service disruption.
The Root Cause: Server-Side Routing or Regional ISP Issues
According to expert analysis, a combination of Error 14, Error 1060, and the "Country isn't supported" message, especially when flipping back and forth, points to a conflict in how Google's backend evaluates a user's location and account flags. Given the widespread and regional nature of the problem, it is highly probable that the cause is a temporary server-side routing issue on Google's end or a localized disruption with how regional Internet Service Providers (ISPs) are routing traffic to Google's authentication servers.
The Solution: Direct Feedback to Google Engineering
When faced with such persistent, server-side glitches, the most effective course of action is to provide direct feedback to Google's engineering team. This process is similar to how you would submit a google meet bug report or report issues with other Google Workspace services.
How to Submit a Diagnostic Report:
- On the Web: If you can get the Gemini page to semi-load, click the Help (Question Mark icon) in the bottom left corner, then select Send Feedback.
- On Android: Tap your profile icon at the top right, then navigate to Help & Feedback, and choose Send Feedback.
Crucial Step: Ensure that the System Logs or Screenshot box is checked before you submit your feedback. This action sends the exact Error 14/1060 metadata stack trace directly to the developers, providing them with the necessary diagnostic information to identify which server node or service is causing the problem in your area.
Where Workalizer Helps
While Workalizer focuses on productivity and operations analytics, it can indirectly help in understanding the impact of such outages. For instance, the Gemini Usage Report can show a sudden drop in activity during an outage, helping administrators identify when usage patterns deviate. Similarly, the Google Workspace Dashboard in Workalizer provides an overview of service health, which, while not pinpointing specific user-level errors, can help track overall service availability and adoption trends over time.
