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:

    • Related Articles

    • Problems with dependencies when running an automation

      This problem usually occurs when the dependencies installation step is not done correctly. When running the code, a message is displayed regarding the installation of the packages: ModuleNotFoundError: No module named 'botcity’ The first step is to ...

    • Resolving SSL certificate verification issues when running commands using 'pip'

      Access blocks are quite common in corporate environments. As a result, you may encounter problems when trying to use BotCity tools and Python resources on a machine in your company's environment. One problem that may occur in these scenarios is the ...

    • What to do when Runner seems stuck when executing a new task?

      In sporadic situations, the Runner may seem stuck after pulling a new task for execution. In this situation, the execution is not started, and the Runner status remains as Executing task ... until the Runner is restarted. Overall, the resources used ...

    • Keeping your remote session active when using Runner

      In some cases where a VM is used to run the automation, keeping the remote session active is necessary to avoid problems with the graphical interface, such as the OSError: screen grab failed error. This error is usually thrown when trying to perform ...

    • How to open a support ticket?

      If the knowledge base articles or our documentation portal did not resolve your questions or issues, you can open a new support ticket through the portal. After detailing the type of support you need, the ticket will be directed to our team so that ...