Skip to content

← All integrations

Linux · Basics

The service agent on Linux servers: discovery of Nginx and Apache, the product packages, and your own scripts for PEM files as a custom agent.

The service agent on the server fetches the task from the appliance over outbound HTTPS on port 443 and installs the certificate locally on the server. The appliance never connects to the server.

What happens

  1. The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
  2. The service agent finds Nginx and Apache on the server, and the product package for the service installs the certificate.
  3. For other services you upload your own script as a custom agent that runs on the server.

Technical details

Connection
The package runs through the service agent on the server. The agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
You need
The service agent installed on the server.
Actions
Depends on the product package or on your own script
Template
custom-linux
Note
  • The custom-linux template shows a script that writes the certificate and key as PEM files with owner and permissions and reloads the service. It is set to run on the appliance (runtime.location: appliance) and must be changed to runtime.location: target before it can be uploaded as a custom agent.
  • Tomcat and WebLogic, which use keystores, have integrations of their own.

Get started