Networker: NVP-vProxy: Registration fails in an IPv6 environment with HTTP code 401

Summary: The vProxy registration fails with invalid credentials and HTTP code 401.

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 integration is configured with the vProxy Appliance. The environment networking is configured with IPv6, and it is not dual-stacked. The vProxy registration fails with invalid credentials and HTTP code 401.

The NetWorker Server logs show: 
160859:nsrvproxy_mgmt: vProxy management job started with CLI: 'C:\Program Files\EMC NetWorker\nsr\bin\nsrvproxy_mgmt.exe register -s [NETWORKER_SERVER_NAME] -v [VCENTER_SERVER_NAME] -h [VPROXY_NAME] -p 9090 -j 13 -k 0 '
161332:nsrvproxy_mgmt: Starting 'amp62-nw-nvp' vProxy registration to '[NETWORKER_SERVER_NAME]' NetWorker server.
161327:nsrvproxy_mgmt: Failed to register vProxy '[VPROXY_NAME]': Cannot get vProxy '[VPROXY_NAME]' state: Possible wrong vProxy userid or password, invalid credentials. Received an HTTP code: 401, libCURL message: "", url: "https://[VPROXY_NAME]:9090/api/v1/VproxyEngines"
161319:nsrvproxy_mgmt: vProxy management job completed with errors.
The vProxy /opt/emc/vproxy/runtime/logs/vrapid/vrapid-engine.log shows: 
YYYY-MM-DD HH:MM:SS NOTICE: Request #1496: Rejecting unauthorized request from '[NSR_LINK-LOCAL_IPV6_ADDRESS]%eth0' for '/api/v1/VproxyEngines':
YYYY-MM-DD HH:MM:SS ERROR:  AdminEngine: sending response error: code=401, errText=Only requests from '[NETWORKER_SERVER_NAME]' are allowed.
YYYY-MM-DD HH:MM:SS TRACE:  Request #1496: Responded to client.

Cause

The NetWorker Server registration request is referencing the Link-Local IPv6 address instead of the IPv6 address. The vProxy appliance does not recognize the Link-Local IPv6 address and rejects the registration request.

Resolution

Workaround:
The NetWorker Server Link-Local IPv6 address can be temporarily removed to allow the vProxy registration. Once the registration is complete, the Link-Local IPv6 address can be restored by rebooting the NetWorker server.
  • Redeploy the vProxy in the environment.
  • Backup the vrapid.service configuration file:
cp -p usr/lib/systemd/system/vrapidd.service usr/lib/systemd/system/vrapid.service_original
  • Edit the vrapid.service configuration file:
vi /usr/lib/systemd/system/vrapid.service
  • Add the command-line argument "--disable-access-control" to the line starting with "ExecStart=".
ExecStart=/opt/emc/vproxy/bin/vrapid --disable-access-control
  • Reload the unit configuration file into systemd:
systemctl daemon-reload
  • Restart the vrapid service engine:
systemctl restart vrapid.service
  • On the NetWorker Server, open on a command prompt window in administrator mode.
  • Determine the Link-local IPv6 Address on the NetWorker Server:
ipconfig /all
  • Remove the Link-local IPv6 Address with the netsh command-line utility:
netsh interface ipv6 delete address interface=[INTERFACE_#] address=[NSR_LINK-LOCAL_IPV6_ADDRESS]
  • Register the vProxy using the NetWorker Management Console.
  • Once the registration is complete, the NetWorker Server can be rebooted to restore the Link-local IPv6 Address.

Products

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