cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Hi Folks,

I get the following error on my Windows File Level backup policy clients for randemly, in order to resolve this issue i always unistall and install the NBU client with reissue token opption...after reinstall the NBU client, backup works fine.
Master server version: 8.1.2

Error Message
=============

status
-------
1: (7647) Proxy peer does not conform to proxy protocol.
2: (7647) Proxy peer does not conform to proxy protocol.

Detailed Job:
------------
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) [PROXY] Connecting host: bak2
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) [PROXY] ConnectionId: {FBA3734E-02AA-11EB-9143-6AEDDA385EE3}Smiley SurprisedUTBOUND
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) [PROXY] pid: 93852
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) [PROXY] Received status: 7647 with message The proxy protocol has been violated. The remote connector of connection ([local] [AF_INET:[12.16.19.154]:43372] -- [remote] [ADDR TRANSLATION ERROR]) is not correctly using the proxy.
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) [PROXY] Encountered error (CERT_PROTOCOL_READING_JSON_LENGTH) while processing(CertProtocol).
30 Sep, 2020 7:24:55 AM - Error bpbrm (pid=13160) bpcd on Server34-bkp exited with status 7647: Proxy peer does not conform to proxy protocol
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) [PROXY] Connecting host: bak2
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) [PROXY] ConnectionId: {FBFB7ADA-02AA-11EB-B693-F68B2C16807C}Smiley SurprisedUTBOUND
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) [PROXY] pid: 93852
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) [PROXY] Received status: 7647 with message The proxy protocol has been violated. The remote connector of connection ([local] [AF_INET:[12.16.19.154]:38899] -- [remote] [ADDR TRANSLATION ERROR]) is not correctly using the proxy.
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) [PROXY] Encountered error (CERT_PROTOCOL_READING_JSON_LENGTH) while processing(CertProtocol).
30 Sep, 2020 7:24:56 AM - Error bpbrm (pid=13160) cannot send mail because BPCD on Server34-bkp exited with status 61: the vnetd proxy encountered an error

30 Sep, 2020 7:24:56 AM - Info bpbkar (pid=0) done. status: 7647: Proxy peer does not conform to proxy protocol
30 Sep, 2020 7:29:05 AM - Info nbjm (pid=5936) starting backup job (jobid=662256) for client Server34-bkp, policy FileSystemBackup, schedule Daily
30 Sep, 2020 7:29:05 AM - Info nbjm (pid=5936) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=662256, request id:{370CA858-F9B8-4D70-907D-2D906739C324})
30 Sep, 2020 7:29:05 AM - requesting resource stu_disk_bak2
30 Sep, 2020 7:29:05 AM - requesting resource bak1.NBU_CLIENT.MAXJOBS.Server34-bkp
30 Sep, 2020 7:29:05 AM - granted resource bak1.NBU_CLIENT.MAXJOBS.Server34-bkp
30 Sep, 2020 7:29:05 AM - granted resource MediaID=@aaaae;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bak2;Path=PureDiskVolume;StorageServer=bak2;MediaServer=bak2
30 Sep, 2020 7:29:05 AM - granted resource stu_disk_bak2
30 Sep, 2020 7:29:05 AM - estimated 3271968 kbytes needed
30 Sep, 2020 7:29:05 AM - Info nbjm (pid=5936) started backup (backupid=Server34-bkp_1601422145) job for client Server34-bkp, policy FileSystemBackup, schedule Daily on storage unit stu_disk_bak2
30 Sep, 2020 7:29:17 AM - started process bpbrm (pid=13160)
30 Sep, 2020 7:29:18 AM - end writing
Proxy peer does not conform to proxy protocol. (7647)

Thanks in advance for answer

5 Replies
Highlighted

Re: Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Hello,

could you check with what user/account these services are started on the client? NetBackup Client Service and the NetBackup Legacy Network Service.

the account must be local system or a user who has the needed permissions.

Highlighted

Re: Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Hi,
Thanks for your responce.

it's domain account withe logon as service rights and for your information using same account other clients are working fine and affected clients also was works fine.

Highlighted

Re: Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Have you checked the host name mappings? When installing/uninstalling the client software, there may have been a time when FQDN was used instead of shortname or vice versa. Also make sure that there aren't any rogue entries for hostname mapping.

 

You can also wipe out the certificate and redeploy it. 

nbcertcmd -listcacertdetails (make sure that the CA certificate is correct)

nbcertcmd -checkclockskew (make sure that, if the certificates are correct, the server times are not more than 5 minutes apart)

If both of these are okay, you can get a new certificate from the master server (you will need a token)

nbcertcmd -GetCACertificate 

nbcertcmd -getcertificate -force (you have to use the -force option to overwrite the existing certificate)

It will then prompt you for the reissue token. You can generate the reissue token from the GUI, copy it, and paste it when prompted.

Highlighted

Re: Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Hi,
Thanks for your responce.

While i'm execute below commands, outputs looks good.

nbcertcmd -listcacertdetails (make sure that the CA certificate is correct)
nbcertcmd -checkclockskew
--------------------------------------------------------

But when i execute below command with -force option i got the following message "Host certificate and certificate revocation list received successfully from server (MasterServer name)" but never asked reissue the token!! hence issue still persists
nbcertcmd -GetCACertificate
nbcertcmd -getcertificate -force

Highlighted

Re: Backup jobs fail- (7647) Proxy peer does not conform to proxy protocol.

Hello try this
Nbcertcmd -getcertificate -force -token
For token, do not use a reissue token, go to token management and create a new one
Then do a bpclntcmd -clear_host_cache on both client and master server.
If problem persists, revoke certificate and do a reset host attribute .
Good luck