---
title: "Why is a container not accessible?"
slug: "why-is-a-container-not-accessible"
updated: 2026-05-27T12:29:01Z
published: 2026-05-27T12:29:01Z
canonical: "docs.insys-icom.com/why-is-a-container-not-accessible"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why is a container not accessible?

If a [container](https://docs.insys-icom.com/kb/docs/container-en) cannot be accessed via its IP address, it is recommended to check the following settings:

- On the *Container → Container* page in the *Container* section:
  - Is the container present and active?
  - Does the container have a configuration?
  - Does the container require a license for being accessed?
- Editing the configuration of the container on the *Container* → *Container* page ( ):
  - Does the container have a bridge into the correct IP net?
  - Is the container configured for the correct IP address?
  - Does the container require a certain user group for being functional?
- Are the IP filters activated on the *Network* → *Firewall / NAT* page? If yes, these may be deactivated temporarily for troubleshooting. If the container can then be accessed, an IP filter rule is missing that permits to access the container.

Why is a container not accessible?