What is OPA?
The on-prem agent (OPA) is software you install in your private IT environment to securely connect it to the Workato cloud. It lets your Workato recipes access resources in your network, such as databases, folders, and on-prem applications, without opening inbound ports in your firewall. On-prem agents are installed in logical groups, called on-prem groups, to achieve high availability and load balancing.
Before you open a ticket
First, check status.workato.com for an ongoing incident. If there is one, follow its updates and check the affected functionality again once it is resolved.
These checks help identify the most common causes of OPA issues, such as DNS, firewall, proxy, or certificate misconfigurations in your environment. Run them on the server where the agent is installed. If a check fails, contact your network or IT team. If all checks pass, open a ticket and include the command-line output.
The commands below use the US data center gateways, sg3.workato.com and sg4.workato.com. If you use a different data center, replace them with the gateway domains listed for your data center in the On-premise gateway addresses document.
1. Check that the gateway name resolves
Use the commands below to verify that the server running OPA can resolve the Workato OPA gateway domains.
Windows/Linux/macOS
nslookup sg3.workato.com
Linux/macOS
dig sg3.workato.com
Repeat for sg4.workato.com. Each name should resolve to three IP addresses.
2. Check connectivity to the gateway
The command below requires curl to be installed on the server with OPA.
On Windows, we recommend using the curl that comes with the Git for Windows package. By default, it could be located at C:\Program Files\Git\usr\bin\curl.exe.
Run the following command from the agent’s home folder:
curl -k -vvv --no-alpn --key conf/cert.key --cert conf/cert.pem https://sg3.workato.com/gateway/ping
Optionally repeat for sg4.workato.com. A healthy result contains the HTTP/1.1 200 OK response and the gateway_version value. If the connection fails or times out, contact your network or IT team.
3. Check the certificate chain
The command below requires OpenSSL to be installed on the server with OPA.
On Windows, we recommend using the OpenSSL that comes with the Git for Windows package. By default, it could be located at C:\Program Files\Git\usr\bin\openssl.exe.
Run the following command:
Linux/macOS
echo | openssl s_client -connect sg3.workato.com:443 2>&1 | grep -E "^ *[0-9]+ s:|^ +i:|Verify return code"
Windows
openssl s_client -connect sg3.workato.com:443
Expected output:
0 s:CN=sg.workato.com
i:C=US, ST=CA, L=Mountain View, O=Workato, OU=Devops, CN=Workato opg CA
1 s:C=US, ST=CA, L=Mountain View, O=Workato, OU=Devops, CN=Workato opg CA
i:C=US, ST=CA, O=Workato Inc., CN=Workato Root CA
Verify return code: 20 (unable to get local issuer certificate)sg4.workato.com. The line Verify return code: 20 (unable to get local issuer certificate) is expected. If a different issuer appears, a proxy or other network equipment is probably inspecting TLS traffic. Ask your network team to exempt the Workato gateway domains from inspection.Information to include
Including the following information in your ticket helps Workato Product Support resolve it faster:
- Details of the issue
- On-prem group ID
- Workspace ID
- Operating system of the host
- OPA logs
- Results of the checks
- Screenshots
- Profile
How to collect it
Details of the issue
Describe the following:
- Detailed steps to reproduce the issue
- What you were trying to achieve and the current result
- The exact error message, if any
- Timestamp of the last occurrence, with time zone
- Any recent changes
- Whether it worked before or is a new setup
On-prem group ID
Go to Control Panel > Tools > On-prem groups.
Click the affected on-prem group.
Copy the ID or the full URL from the browser address bar.
Workspace ID
Each environment (Development, Test, Production) has its own ID. To obtain this ID:
- Open the environment where the issue can be reproduced
- Navigate to Workspace Admin > Settings > General
- Copy the Workspace ID value
Operating system of the host
Windows, Linux, or macOS. If the agent runs in a container, specify Docker.
OPA logs
Collect the agent-YYYY-MM-DD.X.log files for the relevant dates from each server in the group.
Results of the checks
See the "Before you open a ticket" section.
Screenshots
Capture the full error message and the location where it appears.
Profile
The cloud or connection profile configuration (config.yml). See the On-Prem Agent Connection documentation.
Comments
0 comments
Please sign in to leave a comment.