KB ID: 10069
Product: Backup & Recovery
Version: 5.0.0
Published: 2022-02-15
Last modified: 2022-02-15
Problem
I want to utilize proxy to route node traffic through it.
Solution
Edit the vprotect-node.service file which is located in
/lib/systemd/system/vprotect-node.service
Originally this file should look like the one below
[Unit] Description = vProtect Node Wants = vdo.service nfs.service nfslock.service rpcbind.service nfs-server.service nfs-lock.service nfs-idmap.service vprotect-vmware.service After = syslog.target network.target vprotect-server.service vdo.service [Service] User = vprotect ExecStartPre = /usr/bin/vprotect configureNbd ExecStart = /usr/bin/vprotect start ExecStop = /usr/bin/vprotect stop Type = forking Restart = on-failure [Install] WantedBy = multi-user.target
Add the following lines to the [Service] section.
Environment="http_proxy=proxy.address:8080" Environment="https_proxy=proxy.adress:8080" Environment="no_proxy=localhost,127.0.0.1"
Make sure to change proxy.address to the address of Your proxy, it can be either IP address or FQDN. Also set the correct port, in the example above it is 8080
The vprotect-node.service file after modification should look like this
[Unit] Description = vProtect Node Wants = vdo.service nfs.service nfslock.service rpcbind.service nfs-server.service nfs-lock.service nfs-idmap.service vprotect-vmware.service After = syslog.target network.target vprotect-server.service vdo.service [Service] User = vprotect Environment="http_proxy=proxy.address:8080" Environment="https_proxy=proxy.adress:8080" Environment="no_proxy=localhost,127.0.0.1" ExecStartPre = /usr/bin/vprotect configureNbd ExecStart = /usr/bin/vprotect start ExecStop = /usr/bin/vprotect stop Type = forking Restart = on-failure [Install] WantedBy = multi-user.target
After modifying the file You need to reload a systemd file and restart the vprotect node to apply the changes
[root@localhost ~]# systemctl daemon-reload [root@localhost ~]# systemctl restart vprotect-node