Skip to main content

Troubleshooting Account Access and Login

Use this guide when you cannot sign in, cannot see the expected organization or Environment, cannot perform an action in the dashboard, or an API request fails because of authentication or permissions.

Cannot sign in to the dashboard​

Go to dashboard.imgwire.dev and try signing in again in a fresh browser session.

If sign-in still fails:

  • Confirm you are using the same email address that was invited to the organization.
  • Complete any email verification or identity-provider prompt shown during login.
  • Disable browser extensions that block redirects or authentication cookies, then retry.
  • Try a private browser window to rule out a stale session.
  • If your organization uses an identity provider, confirm you still have access through that provider.

Organization or Environment is missing​

Imgwire resources are scoped to an organization and an Environment. If images, API keys, or settings appear to be missing, you may be in the wrong context.

Check:

  • The organization selector in the dashboard header.
  • The Environment dropdown in the dashboard header.
  • Whether the Environment was created for another app, staging, or production context.
  • Whether your user was invited to the organization that owns the Environment.

For setup details, see Set Up Imgwire.

Operation is not allowed​

Dashboard and API operations can require a specific organization role. Imgwire organization roles include OWNER, ADMIN, and DEVELOPER.

If you receive OperationNotAllowedError or a 403 response:

  • Confirm you are in the correct organization.
  • Ask an organization owner or admin to check your role on the Team Members page.
  • Confirm your organization plan includes the feature you are trying to use.
  • For MCP or OAuth-linked tools, confirm the Authorized Connection is linked to the Environment you intend to use.

API key is rejected​

API key errors are usually caused by the wrong key type or wrong Environment.

Check these rules:

  • Server API Keys are environment-scoped and belong only in trusted backend, local, or CI environments.
  • Client Keys are publishable and are intended for frontend upload flows and image lookup.
  • Client Keys cannot manage CORS origins, custom domains, metrics, URL uploads, upload tokens, deletes, or bulk operations.
  • If a Server Key was rotated or deleted, update every backend, CLI, and CI secret using it.
  • If you are using dashboard or OAuth auth instead of an environment-scoped key, include X-Environment-Id when the API requires a target Environment.

See Resource API Overview for authentication conventions.

MCP or agent connection is not working​

The Imgwire MCP server uses OAuth-linked Authorized Connections. Authorized Connections must be scoped to a specific Environment.

If an agent cannot access the expected images or metrics:

  • Re-authenticate the MCP connection.
  • Open Authorized Connections and confirm the connection is bound to the correct Environment.
  • If the MCP tool asks you to choose an Environment, complete that elicitation before retrying the operation.
  • Use the MCP whoami tool to confirm the current user, organization, and linked Environment.

See Using the Imgwire MCP Server.

Some actions require an active organization subscription or plan capability. If access changed after a trial, cancellation, failed payment, downgrade, or plan change, review Billing and Plans.

Last updated at: May 8, 2026