Skip to main content
Version: ACE 5

Frequently Answered Questions

This page contains answers to Frequently Answered Questions

If you are not able to find answer here, then please ask question in ACE support chat

CORS error when testing flow or API​

Problem​

CORS is not configured properly for Designer Server

Solution​

Configure cors as described here

ACE is timing out with HTTP error 504 in Kubernetes environment​

Problem​

Ingress is timing out the requests.

Solution​

Change timeout in ingress definition. See ingress documentation for the additional details.

For example, to set timeout to 10 minutes, add annotations:

    nginx.ingress.kubernetes.io/proxy-connect-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "600"

or in newer versions of ingress controller:

    nginx.org/proxy-connect-timeout: 600s
    nginx.org/proxy-read-timeout: 600s
    nginx.org/proxy-send-timeout: 600s

Requests through ACE are slow​

Problem​

Caching is not enabled

Solution​

How to get ACE Desktop logs​

ACE runtime server logs are available through Docker.

If it's necessary to view Designer Desktop logs, it's possible to start it from command line.

  • Find "ACE Designer.exe" file and start it from command line
  • Example on Windows:
PS C:\Users\<username>\AppData\Local\ace_designer_electron> & '.\ACE Designer.exe'

Large content (413 Content Too Large)​

ACE services running in Kubernetes environment require nginx.ingress.kubernetes.io/proxy-body-size configuration to allow for operations that exceed 1MB in size. If you encounter any issues that exclusively happen for large files or operations, make sure that Kubernetes is configured to support it accordingly.

Scenarios that can possibly be resolved by updating nginx.ingress.kubernetes.io/proxy-body-size configuration:

  • Error on importing large workspace or API - fixed by configuring ace-designer service
  • Error on running API with large file or document - fixed by configuring ace-runtime-server service
  • Error when deploying large amount of schedules - fixed by configuring ace-deployment-server

Getting ECONNREFUSED error when trying to test flow or API in ACE Desktop​

Problem​

ACE runtime server is not reachable outside of docker container using host.docker.internal

Solution​

When using Rancher desktop open Preferences, click on WSL, click on Integrations tab and check Ubuntu.

Schedules or flows are not installed​

Problem​

There is no connectivity to Redis or Mongo

Solution​

Check if there is connectivity to redis and mongo, and connect with IT to resolve the issue.

Redis

  • Run temporary pod in the same namespace as ACE services, for example kubectl run --rm -i --tty nginx-bash --image=nginx --namespace=<namespace> -- bash
  • Install redis-cli by running command apt-get update && apt-get install -y redis
  • Connect to redis by running redis-cli -h <redis-service-name> -p <port> and other parameters if needed

For more details, see the following guide.

Mongo

  • Run temporary pod in the same namespace as ACE services, for example kubectl run --rm -i --tty mongo-bash --image=mongo --namespace=<namespace> -- bash
  • Connect to mongo by running mongosh "<mongo-connection-string>"

For more details, see the following guide.