Broad Matters
Technology

how to fix 2 UNKNOWN: Getting metadata from plugin failed with error: Could not refresh access token: Request failed with status code 500

December 7, 2025

how to fix 2 UNKNOWN: Getting metadata from plugin failed with error: Could not refresh access token: Request failed with status code 500

Quick Fix

This error typically indicates an authentication issue where your plugin cannot refresh its access token. Try re-authenticating the plugin or checking your API credentials and ensuring they haven't expired.

What the Problem Means

The error '2 UNKNOWN: Getting metadata from plugin failed with error: Could not refresh access token: Request failed with status code 500' means that a plugin you are using is attempting to retrieve some data (metadata), but it's failing because it cannot renew its security access token. The 'Request failed with status code 500' further indicates that the server responsible for providing or refreshing this token encountered an internal error, preventing the token refresh process from completing successfully.

Common Causes

  • Expired or invalid API keys/access tokens.
  • Incorrectly configured credentials within the plugin or application.
  • Network connectivity issues preventing communication with the authentication server.
  • Temporary server-side issues (status code 500) with the service that issues/refreshes access tokens.
  • Changes in user permissions or access policies for the account linked to the plugin.
  • Firewall or proxy blocking the outbound requests from the plugin to the authentication service.
  • Plugin misconfiguration or outdated plugin version.

Fast Fixes to Try First

  1. Restart the Plugin/Application: A simple restart can often clear temporary glitches.
  2. Check API Key/Token Expiry: Verify that your API keys or access tokens are still valid and have not expired.
  3. Re-authenticate the Plugin: If the plugin has an option to re-authenticate or reconnect to its service, try performing this action.
  4. Verify Network Connectivity: Ensure your system has stable internet access and can reach the authentication server.
  5. Check System Clock: Incorrect system time can cause SSL/TLS handshake failures, which might manifest as authentication issues.

Advanced Fixes

  1. Regenerate API Keys/Tokens: If feasible, generate new API keys or access tokens from the service provider's dashboard and update them in your plugin configuration.
  2. Review Plugin Configuration: Double-check all plugin settings, especially those related to authentication, endpoints, and scopes.
  3. Inspect Server Logs: If you have access to the server where the plugin is running or the logs of the service it's trying to connect to, look for more detailed error messages around the time the issue occurred.
  4. Check Firewall/Proxy Settings: Ensure no firewalls, proxies, or security groups are blocking outbound connections from your plugin to the necessary authentication endpoints.
  5. Update Plugin to Latest Version: An outdated plugin might have bugs related to token refresh or compatibility issues. Update it if a newer version is available.
  6. Monitor Service Status: Check the status page of the service the plugin connects to for any reported outages or issues.

Device/App Specific Notes

  • Self-Hosted Environments: If the plugin is running on your own server, ensure the server's time is synchronized (NTP) and that outbound ports (typically 443 for HTTPS) are open.
  • Cloud Platforms (e.g., AWS Lambda, Google Cloud Functions): Verify the IAM roles, service accounts, or secret managers used by the plugin have the necessary permissions and that secrets are correctly rotated.
  • Containerized Applications (Docker, Kubernetes): Ensure environment variables or mounted secrets containing credentials are correctly passed to the container and that network policies allow external communication.
  • Specific Plugin Versions: Some versions of plugins might have known issues with token refreshing. Consult the plugin's documentation or community forums.

When to Contact Support

  • You have verified all your credentials are correct and regenerated them, but the error persists.
  • The service status page indicates an ongoing outage or issue with their authentication system.
  • You see a persistent '500 Internal Server Error' from the authentication service, suggesting a problem on their end that you cannot resolve.
  • You lack access to the necessary server logs or configuration options to troubleshoot further.
  • The problem started immediately after a service provider update and affects multiple users or integrations.

Summary

The '2 UNKNOWN: Getting metadata from plugin failed with error: Could not refresh access token: Request failed with status code 500' error signifies a breakdown in the plugin's ability to authenticate itself and retrieve necessary data, often due to expired tokens or server-side issues. Addressing this involves systematically checking authentication credentials, network connectivity, plugin configuration, and potentially regenerating tokens. If the problem persists after thorough troubleshooting, especially if external server issues are suspected, contacting the plugin vendor or service provider's support team is the recommended next step.