NetWorker: Failed to register vProxy with error "Possible wrong vProxy user id or password"

Summary: NetWorker VMware Protection (NVP) vProxy registration fails, reporting possible wrong vProxy user id or password. The admin user and the correct password are specified in the vProxy properties. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The NetWorker VMware Protection (NVP) vProxy registration fails with a NetWorker server. The error reports:

Failed to register vproxy with error "Possible wrong vProxy user id or password"

The same error is repeatedly seen in the NetWorker server's daemon.raw.

You can successfully log in to the vProxy as the admin user over SSH or console connection. 

NOTE: If you cannot log in to the vProxy appliance, see: NVP-vProxy: How to update or change vProxy admin or root password

The daemon.raw may also report similar messaging from the nsrdispd_vproxy process:

nsrdisp_vproxy log report error "NSR notice 10/16/18 11:13:13.717973 LIBNSRVPROXY: Received bytes [0 - 19: Method Not Allowed".

The vProxy appliances /opt/emc/vproxy/runtime/logs/vrapid/vrapid-engine.log reports similar messaging:

2018/10/16 19:08:01 TRACE:  rejecting unauthorized request "/api/v1/VproxyEngines":
2018/10/16 19:08:01 ERROR:  AdminEngine: sending response error: code=401, errText=only requests from networker-server are allowed

Cause

The vProxy Application Programming Interface (API) includes an access-control mechanism for requests. This mechanism validates both the credentials and the source of the request. If the source of the request is from an unauthorized IP or an unexpected hostname, the registration fails with the symptoms outlined above.

In some environments, firewalls, or Network Address Translation (NAT) devices between vProxy and NetWorker server. The source of the RESTAPI request might appear coming from an unexpected IP/hostname, which might also cause this problem.

Resolution

This must be corrected at the network level.

Workaround:

Access control can be disabled on the vProxy appliance to accept the communication through firewall or NAT implementations.

  1. Open an SSH session to the vProxy and login using the admin user account.
  2. Switch to the root account: sudo su -
  3. Open the vrapid service file:  vi /usr/lib/systemd/system/vrapid.service
  4. On the ExecStart line, append the following: 
ExecStart=/opt/emc/vproxy/bin/vrapid --disable-access-control
  1. Save the file.
  2. Restart the vrapid service and reload system daemons:
systemctl daemon-reload
systemctl restart vrapid
  1. After restarting the service, you may try the following command to verify the status: systemctl status vrapid
vrapid.service - vProxy REST API Daemon
   Loaded: loaded (/usr/lib/systemd/system/vrapid.service; enabled)
   Active: active (running) since Wed 2018-12-26 22:09:46 EST; 4s ago
Main PID: 22696 (vrapid)
   CGroup: /system.slice/vrapid.service
             22696 /opt/emc/vproxy/bin/vrapid --disable-access-control
  1. Register the vProxy with the NetWorker server.
NOTE: This setting is not kept across vProxy upgrades. The above process must be followed again on the newly deployed/upgraded vProxy appliance.

Additional Information

NAT implementations impact FLR capabilities:
NVP-vProxy: FLR "Mount failed: Unable to complete Sysinfo operation"

Affected Products

NetWorker

Products

NetWorker Family
Article Properties
Article Number: 000039048
Article Type: Solution
Last Modified: 07 Aug 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.