Set Rundeck's Proxy in the Packaged Service's JVM Defaults
Merge Java proxy properties into RDECK_JVM_OPTS in the RPM or DEB override file, then start the service with those values.
Choose the override file for the installed package:
| Package | Service defaults |
|---|---|
| RPM | /etc/sysconfig/rundeckd |
| DEB | /etc/default/rundeckd |
Merge these properties into its existing RDECK_JVM_OPTS value:
RDECK_JVM_OPTS="-Dhttp.proxyHost=proxy.example.net -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.example.net -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=localhost|127.*|*.internal.example"Preserve the other startup options and apply through the normal service restart. The file affects the next JVM launch, not the running one. For permitted public-service calls, the HTTP proxy list supplies candidates for the HTTP proxy host and port fields. Rundeck documents these package override locations; editing /etc/rundeck/profile directly can be overwritten on upgrade.
Use this route for clients honoring Java proxy properties inside the Rundeck JVM. A job's external program or plugin-owned transport can need another input. Identify the failed operation before applying the service defaults to it.