Jason Posted May 7, 2021 Share Posted May 7, 2021 Hi. have been using Nakivo for over 5 years. Has anyone else had issues with the 10.3 update on Synology NAS units? First after upgrading the certificates for the transporters would not work and I had to rename them. Now my offisite transporter on my offsite NAS units will not accept connections on 9446. i am stuck with no off site backups. yes I have a ticket open but looking for feedback form the community. I do not want to go all weekend without offsite backups 1 Quote Link to comment Share on other sites More sharing options...
Mario Posted May 11, 2021 Share Posted May 11, 2021 Hi Jason I'm still on 10.2, so I can't help with your issue... Did you get solution from support? I also use Synology and like to know if it's a showstopper. Thanks Mario 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 11, 2021 Share Posted May 11, 2021 On 5/7/2021 at 5:36 PM, Jason said: Hi. have been using Nakivo for over 5 years. Has anyone else had issues with the 10.3 update on Synology NAS units? First after upgrading the certificates for the transporters would not work and I had to rename them. Now my offisite transporter on my offsite NAS units will not accept connections on 9446. i am stuck with no off site backups. yes I have a ticket open but looking for feedback form the community. I do not want to go all weekend without offsite backups Hi, @Jason! If you have a "CERTIFICATE_EXPIRED" for transporter after update to v10.3 please do the following: - ssh to your Synology where Nakivo Instance is installed. - cd /volume1/@appstore/NBR/transporter. - Stop Nakivo Services on Synology. Check how to do it here https://helpcenter.nakivo.com/display/KB/Starting+and+Stopping+Product+Services - mv certificate.pem certificate.pem_orig. - Start Nakivo services. - refresh transporter (connect/accept the certificate). The detailed guide is here https://helpcenter.nakivo.com/display/NH/Refreshing+Transporter+Details#RefreshingTransporterDetails-ManuallyRefreshingaSingleTransporter If the problem persists, please generate and send us a Support Bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles Let me know if this worked for you. 1 Quote Link to comment Share on other sites More sharing options...
Jason Posted May 11, 2021 Author Share Posted May 11, 2021 Hi. The problem is not with the certificates anymore. The offsite transporter and repository are not accessible from the On Site Synology NAS install. The connection to "X.X.X.X:9446" was refused. Make sure the provided information is correct and the connection is not blocked. I have setup a Telnet session and can successfully connect to that IP form my onsite network using port 9446 I have a ticket open but they have told me it is off to development to work on the issue. I currently have no offsite backups and entering my 2nd week. 1 Quote Link to comment Share on other sites More sharing options...
Jason Posted May 11, 2021 Author Share Posted May 11, 2021 4 hours ago, Mario said: Hi Jason I'm still on 10.2, so I can't help with your issue... Did you get solution from support? I also use Synology and like to know if it's a showstopper. Thanks Mario Hi Mario, My suggestion is to hold off if you have a set up like mine. Onsite Nakivo - Synology NAS Connects through a Site-to-Site VPN over WAN to Offsite Nakvio - Synology NAS I use Backup Copy jobs for my offsite transfers and can no longer use that system due to the transporter connection being blocked. Entering my 2nd week as you can see from the post above. Quote Link to comment Share on other sites More sharing options...
Boris Posted May 12, 2021 Share Posted May 12, 2021 On 5/11/2021 at 10:14 AM, Official Moderator said: Hi, @Jason! If you have a "CERTIFICATE_EXPIRED" for transporter after update to v10.3 please do the following: - ssh to your Synology where Nakivo Instance is installed. - cd /volume1/@appstore/NBR/transporter. - Stop Nakivo Services on Synology. Check how to do it here https://helpcenter.nakivo.com/display/KB/Starting+and+Stopping+Product+Services - mv certificate.pem certificate.pem_orig. - Start Nakivo services. - refresh transporter (connect/accept the certificate). The detailed guide is here https://helpcenter.nakivo.com/display/NH/Refreshing+Transporter+Details#RefreshingTransporterDetails-ManuallyRefreshingaSingleTransporter If the problem persists, please generate and send us a Support Bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles Let me know if this worked for you. I have the same Problem after Update Nakivo on QNAP to v10.3 (from 10.2) the Onboard Transporter shows Error I do the same like for Synology except the changed Path cd /share/CACHEDEV1_DATA/.qpkg/NBR/transporter After this a new certificate.pem is created, but now the transporter and the repository are inassesibel, and refresh will not work The "Onboard repository" backup repository is inaccessible The "Onboard transporter" transporter assigned to the "Onboard repository" backup repository is inaccessible. Make sure the transporter is available. The "Onboard transporter" transporter is inaccessible An internal error has occurred. Reason: unspecified error. MfG Boris 1 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 13, 2021 Share Posted May 13, 2021 On 5/11/2021 at 1:41 PM, Jason said: Hi. The problem is not with the certificates anymore. The offsite transporter and repository are not accessible from the On Site Synology NAS install. The connection to "X.X.X.X:9446" was refused. Make sure the provided information is correct and the connection is not blocked. I have setup a Telnet session and can successfully connect to that IP form my onsite network using port 9446 I have a ticket open but they have told me it is off to development to work on the issue. I currently have no offsite backups and entering my 2nd week. Hi, @Jason! So our Support team could resolve your issue, please generate and send us a new support bundle with the main database included for further investigation. https://helpcenter.nakivo.com/display/NH/Support+Bundles#SupportBundles-CreatingSupportBundles Let me know if I can help with anything else. Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 14, 2021 Share Posted May 14, 2021 On 5/12/2021 at 11:37 PM, Boris said: I have the same Problem after Update Nakivo on QNAP to v10.3 (from 10.2) the Onboard Transporter shows Error I do the same like for Synology except the changed Path cd /share/CACHEDEV1_DATA/.qpkg/NBR/transporter After this a new certificate.pem is created, but now the transporter and the repository are inassesibel, and refresh will not work The "Onboard repository" backup repository is inaccessible The "Onboard transporter" transporter assigned to the "Onboard repository" backup repository is inaccessible. Make sure the transporter is available. The "Onboard transporter" transporter is inaccessible An internal error has occurred. Reason: unspecified error. MfG Boris Hello, @Boris! Most likely, our Support Team has to establish a remote session to resolve your issue. Please send a support bundle so that you could get personalized help from our specialists. Here you can check how to generate a support bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles#SupportBundles-CreatingSupportBundles If you have any doubts, don't hesitate to contact me! 1 Quote Link to comment Share on other sites More sharing options...
mikeg Posted May 18, 2021 Share Posted May 18, 2021 Seeing identical issues, tried a new 10.3 ova and it has problems with generic transporter errors that are useless for troubleshooting. 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 19, 2021 Share Posted May 19, 2021 Hello, @mikeg! Have you sent a Support Bundle yet? Let me know if you need any help with generating it. Quote Link to comment Share on other sites More sharing options...
Boris Posted May 20, 2021 Share Posted May 20, 2021 On 5/14/2021 at 11:05 AM, Official Moderator said: Hello, @Boris! Most likely, our Support Team has to establish a remote session to resolve your issue. Please send a support bundle so that you could get personalized help from our specialists. Here you can check how to generate a support bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles#SupportBundles-CreatingSupportBundles If you have any doubts, don't hesitate to contact me! Problem ix fixed via remote connection from the great support Team... thx for the fast fix 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 20, 2021 Share Posted May 20, 2021 @Boris, I am glad to hear that your issue is solved now. Don't hesitate to contact us if you have any doubt! Quote Link to comment Share on other sites More sharing options...
LIS GmbH Posted May 28, 2021 Share Posted May 28, 2021 Hello, i drop the old 'onboard transporter' and create an new one. That work for me. 1 Quote Link to comment Share on other sites More sharing options...
Mario Posted May 28, 2021 Share Posted May 28, 2021 I'm doing the update right now. I have the same error and requested support for this. Conclusion: if you can wait with the upgrade, then wait.... 1 Quote Link to comment Share on other sites More sharing options...
Mario Posted May 28, 2021 Share Posted May 28, 2021 Well, something is strange. At version 12.2 all system are working correct, now after the update of today i get the follwoing error: Certificate of this transporter has expired on 27 Dec 2020 at 16:31 (UTC +01:00). Replace the certificate to continue using this transporter Why was a certificate workting till today, when it expired 6 month ago? @Official Moderator can you share the information on the forum so that everyone can benefit? 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted May 28, 2021 Share Posted May 28, 2021 @Mario, I redirected your question to our Support Team. As soon as I have a response, I'll let you know. Quote Link to comment Share on other sites More sharing options...
Boris Posted May 28, 2021 Share Posted May 28, 2021 (edited) On 5/20/2021 at 11:26 AM, Boris said: Problem ix fixed via remote connection from the great support Team... thx for the fast fix Here is how to fix it... for QNAP Login to QNAP via SSH admin cd /share/CACHEDEV1_DATA/.qpkg/NBR/transporter # ./nkv-bhsvc stop Stopping NAKIVO Backup & Replication Transporter service: [/share/CACHEDEV1_DATA/.qpkg/NBR/transporter] # ./bhsvc -b "<UsePassword>" [/share/CACHEDEV1_DATA/.qpkg/NBR/transporter] # ./nkv-bhsvc start Starting NAKIVO Backup & Replication Transporter service: Use Crome Browser https://<qnapip>:4443 Go to Settings / Transporters / Onboard transporter / Edit Press F12 -> go to Console and type following JavaScript codes (Paste one by one command and Press Enter): var a=Ext.ComponentQuery.query("transporterEditView")[0] a.masterPasswordContainer.show() a.connectBtn.show() you get new fields in the Browser: - Master password: - Connect Button In Master password: <ThePassworfromTheSSHCommand> (Same as used here in the bhsvc -b "<UsePassword>") Press Connect Button Then Refresh Transporter an Repository by Boris Edited May 28, 2021 by Boris Change some info 1 1 Quote Link to comment Share on other sites More sharing options...
Boris Posted May 28, 2021 Share Posted May 28, 2021 2 hours ago, Mario said: I'm doing the update right now. I have the same error and requested support for this. Conclusion: if you can wait with the upgrade, then wait.... Try This https://forum.nakivo.com/index.php?/topic/5883-103-issues/&do=findComment&comment=6743 1 Quote Link to comment Share on other sites More sharing options...
Mario Posted May 28, 2021 Share Posted May 28, 2021 Hi Boris Thank you for this trick I did a reinstall of all the needet stuff, it took the complete day but now it's working again. (Multi tenant setup) 1 Quote Link to comment Share on other sites More sharing options...
Mario Posted June 1, 2021 Share Posted June 1, 2021 I've got the following link from support: https://maglar.box.com/shared/static/ebzm01v0080ibtvdh2ubc11s7ops58wa.sh This is a newer build, and it should fix the problems. Since I was able to fix the problems with reinstall, I won't upgrade. But maybe some else can minimize his trouble. Mario 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted June 1, 2021 Share Posted June 1, 2021 @Mario, thank you for sharing! Quote Link to comment Share on other sites More sharing options...
nicojmb Posted June 8, 2021 Share Posted June 8, 2021 @Boris Works like a charm! 1 Quote Link to comment Share on other sites More sharing options...
AnneMcGrath Posted June 16, 2021 Share Posted June 16, 2021 (edited) Hi, oh how nice that I found your tutorial, after updating 10.3 I had not just everything did not work, but stupid everything flew and I could not do anything. I don't know what caused it, but I'm going to reinstall using your guide! Thank you so much. Edited June 16, 2021 by AnneMcGrath 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted June 16, 2021 Share Posted June 16, 2021 @AnneMcGrath, thank you too for your feedback! I'm glad you know what to do now. If you have any question, don't hesitate to contact me Quote Link to comment Share on other sites More sharing options...
MYG63 Posted June 17, 2021 Share Posted June 17, 2021 Hello there, Is there any way to make it running on a Synology? I have same problem here with 2 Synology's I just updated from 10.1 (running environment over 1/2 year) to 10.3 and there is no more connection to transporter reported. Version shown in packet manager on both sides is 10.3.0.55051-1000 Message in transporter info is: The "xxxx-transporter" transporter is inaccessible The connection to "192.168.xxx.xxx:9446" was refused. Make sure the provided information is correct and the connection is not blocked. Please provide way to get rid of that error. 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.