Traffic Portal is only supported on CentOS Linux distributions version 7.x and 8.x. It runs on NodeJS and requires version 16 or higher.
Build the Traffic Portal RPM using the instructions in Building Traffic Control.
Copy the Traffic Portal RPM to your server
Install NodeJS. This can be done by building it from source, installing with yum(8) if it happens to be in your available repositories (at version 16+), or using the NodeSource setup script.
curl --silent --location https://rpm.nodesource.com/setup_16.x | sudo bash -
Traffic Portal is primarily configured through three different files that affect different parts of its behavior. Those files are detailed in this section.
module.exports to the value of a configuration object. Configuration objects have the following allowed properties.
If Traffic Portal is being upgraded, reconcile
config.js.rpmnew and then delete
The properties of this object control Traffic Portal’s interactions with the Traffic Ops API.
The full URL that points to the root of the Traffic Ops API, e.g.
The properties of this object describe system paths important to Traffic Portal (other than SSL-related files, which are kept in the
The directory where the built Traffic Portal front-end files are kept. In most cases, changing this from the default is unnecessary/discouraged.
The properties of this object describe the logging behavior of Traffic Portal. If this property is missing, or is
null(or other “falsey” values), then logging is done simply on STDOUT.
Defines a file location for Traffic Portal’s access logs. If this property is missing, or is
null(or other “falsey” values), then logs will go to STDOUT instead.
A port number that sets the port on which Traffic Portal will listen for insecure (HTTP) connections. If
false, requests made to this port will be redirected to use HTTPS on the
sslPortinstead of just serving content insecurely.
A boolean that defines whether or not Traffic Portal will reject SSL certificates that fail to validate as trusted.
Setting this to
falseexposes Traffic Portal to security vulnerabilities such as man-in-the-middle attacks, and should never be done in a production setting.
This object has properties that set the locations of SSL keys and certificates. Has no effect if
The file location of the SSL certificate private key.
The file location of the x509 SSL certificate that Traffic Portal will use.
The file locations of the full certificate chain for the certificate authority that signed the SSL key (in order).
A port number that sets the port on which Traffic Portal will listen for secure (HTTPS) connections. Has no effect if
A boolean that defines whether or not the Traffic Portal instance will offer secure (HTTPS) connections.
Setting this to
falsecan expose sensitive data such as authentication credentials. Do not ever do that in a production setting.
This property defines the maximum time for which Traffic Portal will process requests before sending a timeout response. It can be either a number of milliseconds, or a duration string accepted by the ms library.
Slow requests will continue to use CPU and memory, even though a response has already been sent to the client.
/opt/traffic_portal/public/traffic_portal_properties.json(if Traffic Portal is being upgraded, reconcile
traffic_portal_properties.json.rpmnewand then delete
This CSS file is provided for users to insert CSS to override the default styling of Traffic Portal.
Configuring OAuth Through Traffic Portal
Starting Traffic Portal
systemctl start traffic_portal
Stopping Traffic Portal
systemctl stop traffic_portal
Using Traffic Portal
- Traffic Portal - Using
- Change Logs
- Sidebar Bottom Buttons
- User Admin