Jump to content
NAKIVO Community Forum

10.3 Issues?


Recommended Posts

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

  • Like 1
Link to comment
Share on other sites

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

  • Like 1
Link to comment
Share on other sites

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.

  • Sad 1
Link to comment
Share on other sites

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.

 

  • Like 1
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

  • Like 1
  • Sad 1
Link to comment
Share on other sites

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.
 

Link to comment
Share on other sites

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!

  • Sad 1
Link to comment
Share on other sites

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

  • Like 1
Link to comment
Share on other sites

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?

  • Like 1
Link to comment
Share on other sites

Posted (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

image.thumb.png.122b058cba6d3813bb4a08f328a35120.png
  
In Master password:  <ThePassworfromTheSSHCommand>            (Same as used here in the bhsvc -b "<UsePassword>")
Press Connect Button

Then Refresh Transporter an Repository

by

Boris

 

Edited by Boris
Change some info
  • Like 1
  • Haha 1
Link to comment
Share on other sites

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 by AnneMcGrath
  • Like 1
Link to comment
Share on other sites

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.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...