DSM Update Version: 6.2.2-24922-4

[wwwampy]

Ok, time to update. I hope it all goes well. Also, I hope I don't meet mister .

 

[wwwampy]

Great, it all went well. No issues so far.

 

[x1xett]

After this update I got problems with Hyper Backup and rsync "folder sync" to a second synology nas. Both tasks are failing, source nas (DS412+) says that destination nas (DS212J) is unreachable.
Also, within DSM -> "Support Center" -> "Contact support" is broken , just a white window with no content.
But "Support Center" -> "Support Services" works as before

 

[jeyare]

After this update I got problems with Hyper Backup and rsync "folder sync" to a second synology nas. Both tasks are failing, source nas (DS412+) says that destination nas (DS212J) is unreachable.
Also, within DSM -> "Support Center" -> "Contact support" is broken , just a white window with no content.
But "Support Center" -> "Support Services" works as before

for me Hyper backup folder sync works uninterrupted after the upgrade.
Checked also few files for Restore. Works.

 

[x1xett]

for me Hyper backup folder sync works uninterrupted after the upgrade.
Checked also few files for Restore. Works.

I have a firewall in front of the destination nas and I can see in the logs that the connection attempt is allowed on the outgoing interface. So something has happened on the recieving nas :/
I also tried to create a new user on the destination nas and reconfigured the backup tasks to use that user instead but with the same result....
Do you have any ideas on what else I could try?

 

[Rusty]

Hypebackup version are up to date on both sides?

 

[jeyare]

Hypebackup version are up to date on both sides?

for me it's running between two diff. DSM ver. (new one and old 6.2.2-24922)

 

[x1xett]

Hypebackup version are up to date on both sides?

In my case they are both the same. But something wierd happened, at 23:59 this night it started working again without me doing anything. Time to dig the logs....

 

[jeyare]

Christmas

 

[WST16]

I like the current one, it’s been good to me.

I take it back.

 

[WST16]

Since I was “forced” rather early to update my 118 because of the certificate fiasco, I thought I might as well update the 216.
I did yesterday and so far (almost) all seems fine.

An issue remains (from previous update) with the shared links expiry dates, on my two stations:

 

[fredbert]

I haven't had LE renewal issues. Being aware that have been for those that updated to the problematic Update 3 and then 4 I manually renewed two certificates that were expiring a few days ago. That went ok for me.

 

[WST16]

I guess you caught it before it attempted the suicide stunt. Good for you

 

[Telos]

I manually renewed two certificates that were expiring a few days ago. That went ok for me.

Good to know. I have a renewal in 9 days.

 

[fredbert]

Good to know. I have a renewal in 9 days.

The first renewal, my default cert and used for main non-web packages (e.g. RADIUS), seemed to take quite a while to complete the process. The second renewal was a lot quicker, it's used for main web-interface packages (e.g. Moments). O walked away and left the NAS do its stuff.

My fallback is a text file that records each certificate's text entered for each field. Plus what is assigned to it. Makes it a bit quicker to recreate if it goes wrong.