Workato · On-prem agent
Failed to start SDK extension. 520 Connection Failed
Short answer
This error means the SDK handshake between an on-prem extension and the Workato platform failed during startup. Build the extension with JDK 8 and make sure its post() URLs use the correct port.
VerifiedLast verified
01Error text
Failed to start SDK extension. 520 Connection Failed02Likely causes
- The SDK handshake between the extension and the Workato platform failed to initialize during startup.
- A missing, wrong or blocked port causes a 520 error.
03How to fix it
- Use JDK version 8.
- Run
./gradlew jarin the extension project root. The output is inbuild/libs/. - Make sure
post()URLs use the correct port, for examplelocalhost:3000.
04Official documentation
→Related errors
- No profile found (Kafka on-prem)"No profile found" means the on-prem agent cannot locate the Kafka profile named in the connection when the job runs. It is usually a config.yml mismatch, so check the kafka block, the profile name and the indentation.
- AgentNonRecoverableException: Error connecting to the gatewayThis on-prem agent error means the agent cannot complete a trusted HTTPS connection to the Workato gateway. The usual cause is SSL inspection, a proxy or a firewall intercepting the connection, so create an exception for the Workato gateways or configure the proxy in config.yml.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer