---
name: Registry-ts_private
title: Why am I getting errors about using a private network in Container Registry?
description: 'You have a valid IAM API key or OAuth token, but you still get an `Access denied` error over a private network in IBM Cloud® Container Registry: `Private-only access is enabled on this account, but this request was over the public network.`'
last-updated: 2024-04-25
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/Registry?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why am I getting errors about using a private network in Container Registry?
{: #troubleshoot-private}
{: troubleshoot}
{: support}

You have a valid IAM API key or OAuth token, but you still get an `Access denied` error over a private network in IBM Cloud® Container Registry: `Private-only access is enabled on this account, but this request was over the public network.`
{: shortdesc}

When you try to access Container Registry, you get the following message:
{: tsSymptoms}

`Private-only access is enabled on this account, but this request was over the public network. You must access this account over the private network`

You attempted to access Container Registry over the public network, but the account is set to allow only private network traffic.
{: tsCauses}

Check the account settings for private only traffic. If private-only traffic is enabled, ensure that you are accessing Container Registry from the private network. For more information, see [Using private network connections](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_private&format=markdown#registry_private_images).
{: tsResolve}