Official Moderator Posted June 22, 2021 Share Posted June 22, 2021 Hello,@MYG63! So that our Support team could address your particular issue, please generate a new support bundle with the option "Include main database" and send it to us for further investigation. If you aren't sure how to create a support bundle, check it here https://helpcenter.nakivo.com/display/NH/Support+Bundles Let me know if I can help you with anything else. Quote Link to comment Share on other sites More sharing options...
MYG63 Posted June 22, 2021 Share Posted June 22, 2021 (edited) Hello, I did already sent a support bundle and the problem was solved online by support team. Great work! The problem was that the older installations which were updated from 9.x to 10.1 and then to 10.3 reported an outdated certificate. This was solved by renaming two files like described here in the thread. A newer installation which was updated from 10.1 to 10.3 did not have the problem. So our 3 sides are running well now. Thank you to all these guys here. Edited June 22, 2021 by MYG63 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted June 22, 2021 Share Posted June 22, 2021 @MYG63, I am glad to hear that. Our Support Team is always here to help you! Quote Link to comment Share on other sites More sharing options...
Sergio_BO_ Posted July 5, 2021 Share Posted July 5, 2021 Same problem with NAKIVO Appliance and Transporter + Repository on SYNOLOGY Same trick wor like a charm BUT: First stage on SYNOLOGY /volume1/@appstore/NBR-Transporter# ./nkv-bhsvc stop ./bhsvc -b "<UsePassword>" Aftter these restart Service from Synology console Connect to NAKIVO Console , edit Transporter , Connect .et voila :)) 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted July 6, 2021 Share Posted July 6, 2021 @Sergio_BO_, I am glad it worked for you! Thank you for the Synology variation contribution. Quote Link to comment Share on other sites More sharing options...
Sergio_BO_ Posted August 13, 2021 Share Posted August 13, 2021 On 7/5/2021 at 6:01 PM, Sergio_BO_ said: Same problem with NAKIVO Appliance and Transporter + Repository on SYNOLOGY Same trick wor like a charm BUT: First stage on SYNOLOGY /volume1/@appstore/NBR-Transporter# ./nkv-bhsvc stop ./bhsvc -b "<UsePassword>" After that Start Service Go to Chrome on Transporter Edit Open console F12 write Ext.ComponentQuery.query("transporterEditView")[0].passwordTextBox.enable(); Now write Password on the Password Field 1 Quote Link to comment Share on other sites More sharing options...
CHEOPSken Posted September 20, 2021 Share Posted September 20, 2021 Hello everyone. I had the same issue on a virtual applience. Boris solution worked for me as well. 1. Connect to the Transporter via SSH (for instance with Putty) 2. cd /opt/nakivo/transporter 3. ./bhsvc stop ./bhsvc -b "<UsePassword>" (creates a masterpassword) ./bhsvc start 4. Go to the Nakivo configuration > Transporter > edit > enter the masterpassword and connect > accept the certificate 5. Fixed and working again. Cheers 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.