If you're trying to install BotCity Studio or start the BotCity Runner and the installation gets stuck at 0%, or you experience authentication or login errors, it is very likely that your corporate environment is blocking the required network access.
This issue is common in corporate networks that enforce strict security and internet access policies.
The following behaviors are frequently observed in restricted environments:
Installer (Wizard) stuck at 0%.
Login failure in BotCity Studio.
Authentication error when launching the BotCity Runner.
BotCity tools require internet access to communicate with cloud services, authenticate users, and install packages. When this communication is blocked by firewalls, corporate proxies, or network restrictions, these errors can occur.
Contact your company’s IT team and request that the following network access rules be whitelisted to ensure proper functioning of BotCity tools.
The Maestro orchestrator runs in the cloud, and the Runner needs to communicate with it via HTTPS (port 443). This port must be open for outbound traffic, but it is not actively occupied by the Runner.
Service Type | URL |
---|---|
Communication with Maestro | https://*.botcity.dev/ |
BotCity SDK access | https://sdk.botcity.dev/ |
Authentication service | https://auth.botcity.dev/ |
If you're using Python for automation development, ensure that the required tools and external package repositories are accessible.
Required tools: pip
, virtualenv
, and setuptools
Service | URL |
---|---|
Official Python Package Index (PyPI) | https://pypi.org/* |
Package hosting domain | https://files.pythonhosted.org/ |
files.pythonhosted.org
is used by PyPI to host package versions. If this URL is blocked, package installation with pip
may fail.Installation and authentication issues in BotCity tools are often caused by restricted corporate networks. Once the necessary URLs and ports are whitelisted, the tools should function as expected.
For more technical information, visit the official BotCity documentation.