Problems with blocking environments

Problems with blocking environments

If you are trying to use BotCity's tools in a corporate environment, you may encounter some issues related to environment locks.

Here are some of the most common issues when using the BotCity Studio SDK in blocking environments:

  • Installation through the Wizard is stuck at 0%.
  • Failed to log in to BotCity Studio.
  • Authentication error when starting BotCity Runner.

If you have observed any of the issues above, we recommend contacting your company's IT team and requesting the following access permissions:

Connecting to BotCity Maestro

The Maestro orchestrator works in the cloud, and the Runner communicates with the Maestro via HTTPS (443), but it does not occupy this port; it just needs it to be open for communication.

Requirements for using BotCity tools in blocking environments:

  • Firewall permission to access https://*.botcity.dev/ (port 443 HTTPS)
  • Firewall permission to access https://sdk.botcity.dev/ (port 443 HTTPS)

Using Python in automation development

If Python is used to develop automation, it will be necessary:

  • Firewall permission to access https://pypi.org/* (Python Package Index - PyPI)
  • Python 3.8 or higher installed
  • Installation of the pip, virtualenv and setuptools packages

Using Java in automation development

If Java is used to develop automation, it will be necessary: