Related Articles

KB44172 - Backup/restore binary configuration using REST API

KB43942 - Example REST commands to add or delete vTMs to the Services Director using curl.

KB43778 - Node management broken in vTM 18.1

KB44587 - How to create a global Virtual Traffic Manager cluster?

6339 - Uploading a locally executable file via the vTM REST API does not make the file executable in directory.

5888 - When running the wizard to 'Join a Cluster' on a new virtual Traffic Manager finishes, the following error appears, "Unable to join Application firewall Cluster, Incorrect username/password'

SA43681 - 2016-11: CSRF vulnerability with Brocade Virtual Traffic Manager (vTM) (CVE-2016-8201)

5580 - How can we configure different values of the vTM's WAF enforcer_max_body_size for different virtual servers?

14120 - Audit log message for pool node changes made via REST API do not include the IP of the node that was changed

4423 - A vTM backend node correctly marked as failed by Passive Monitor is not recovering when the node is contactable.

< Back to search results

Article

5443 - The vTM's REST API is enabled but not running

« Go Back

Information

Last Modified Date	6/6/2018 10:30 AM

Synopsis

The REST API is enabled but not running.

Environment:
All versions

Problem or Goal

Cause

Solution

The check for the REST API is done on localhost. If you use Access Restrictions, adding 127.0.0.1 to the list at System > Security > Restricting Access should solve the issue.

Go to SYSTEM > SECURITY > Restricting Access > Allow access from: 127.0.0.1/32

Related Links

Attachment 1

Created By	VenkataKondaReddy Palem