# WARNING: connection is not using a post-quantum key exchange algorithm.

**URL:** <https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175>\
**Category:** Backup and data protection\
**Tags:** quts-hero, backup\
**Created:** [June 8, 2026, 7:26pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175 "2026-06-08T19:26:53Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![amnesia](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@amnesia](https://community.qnap.com/u/amnesia)\
**Post date:** [June 8, 2026, 7:26pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/1 "2026-06-08T19:26:53Z")

</div>

Following the upgrade to the QuTS hero h6.0.0.3500, I encountered an issue with the HBS 3 backup of the servers installed on Rocky Linux via rsync. The error message is logged in the log and sent via email after the backup job fails.

Device Name: NAS03  
Severity: Error  
Date/Time: 2026/06/08 15:43:33

App Name: Hybrid Backup Sync  
Category: Job Status  
Message: [Hybrid Backup Sync] Failed to complete Sync job: "server9.web.home.int. Encountered error "\*\* WARNING: connection is not using a post-quantum key exchange algorithm. "

It has been observed that the QuTS hero v6 uses OpenSSH v10, while the algorithm utilized on Rocky Linux (OpenSSH v9) falls short of meeting the required standards. To rectify this situation, the following steps should be executed on the Rocky Linux-powered servers:

1. vim /etc/ssh/sshd\_config

and add the following line at the end of the file:

`KexAlgorithms mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512`

1. systemctl restart sshd && systemctl status sshd - confirm that sshd is running
2. update-crypto-policies --set DEFAULT:PQ - and restart the host afterwards

It took me some time to identify the issue, so I hope this information proves beneficial to you.

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [June 9, 2026, 3:42pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/2 "2026-06-09T15:42:27Z")

</div>

To be clear: This is NOT a QNAP issue. It’s an issue with your implementation on your Linux server.

Your title makes it sound like it’s a QNAP problem…

---

<div class="post-metadata">

**Author:** ![amnesia](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@amnesia](https://community.qnap.com/u/amnesia)\
**Post date:** [June 9, 2026, 3:58pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/3 "2026-06-09T15:58:12Z")

</div>

I did not assert that the issue was related to the Qnap or HBS. It is evident that the problem is associated with the encryption algorithm employed on the Rocky Linux servers utilizing OpenSSH v9. Since I was unable to find any information regarding this, I simply posted the issue and the corresponding resolution steps.

In contrast, the issue lies not with my implementation but rather with the default encryption settings of the SSH server in the Rocky Linux distribution. I highly doubt that you intentionally included `mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com` algorithms in your SSH configuration file.

---

<div class="post-metadata">

**Author:** ![JackWang](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@JackWang](https://community.qnap.com/u/JackWang)\
**Post date:** [June 10, 2026, 10:15am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/4 "2026-06-10T10:15:51Z")

</div>

Hi,

Thank you for reporting this.

We have confirmed that the warning is caused by the OpenSSH update when the remote side does not use a post-quantum key exchange algorithm. Although the rsync transfer may complete successfully, HBS may incorrectly treat this SSH warning output as an error and mark the job as failed.

We have identified the cause and will include a fix in the next release.

Thank you for your understanding.

---

<div class="post-metadata">

**Author:** ![Flintstone](https://avatars.discourse-cdn.com/v4/letter/f/aeb1de/32.png) [@Flintstone](https://community.qnap.com/u/Flintstone)\
**Post date:** [June 16, 2026, 7:05am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/5 "2026-06-16T07:05:39Z")

</div>

Please fix this now. I make a backup using rsync three times per day, and since today, it no longer works.

---

<div class="post-metadata">

**Author:** ![uff.ack](https://avatars.discourse-cdn.com/v4/letter/u/a587f6/32.png) [@uff.ack](https://community.qnap.com/u/uff.ack)\
**Post date:** [June 16, 2026, 7:35am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/6 "2026-06-16T07:35:57Z")

</div>

Same problem here too, a quick fix on qnap side is needed.

---

<div class="post-metadata">

**Author:** ![amnesia](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@amnesia](https://community.qnap.com/u/amnesia)\
**Post date:** [June 16, 2026, 8:19am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/7 "2026-06-16T08:19:33Z")

</div>

The solution is described in the first post. No need to wait for the Qnap. After all, this is not an issue, and there is nothing broken. Read the post.

---

<div class="post-metadata">

**Author:** ![uff.ack](https://avatars.discourse-cdn.com/v4/letter/u/a587f6/32.png) [@uff.ack](https://community.qnap.com/u/uff.ack)\
**Post date:** [June 16, 2026, 8:43am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/8 "2026-06-16T08:43:01Z")

</div>

The way SSH works dictates that the client has the absolute right and duty to decide and declare how it wants to connect. There should be an option to achieve this without relying on the autorun workaround; furthermore, the issue where HBS incorrectly treats this SSH warning output as an error needs to be fixed

---

<div class="post-metadata">

**Author:** ![Flintstone](https://avatars.discourse-cdn.com/v4/letter/f/aeb1de/32.png) [@Flintstone](https://community.qnap.com/u/Flintstone)\
**Post date:** [June 18, 2026, 6:50am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/9 "2026-06-18T06:50:00Z")

</div>

The fix may work for Rocky Linux specifically, but it does not work if you have a subscription to an external server which does not provide for a post-quantum key exchange algorithm.

---

<div class="post-metadata">

**Author:** ![kahilzinger](https://avatars.discourse-cdn.com/v4/letter/k/e99b99/32.png) [@kahilzinger](https://community.qnap.com/u/kahilzinger)\
**Post date:** [June 23, 2026, 7:01pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/10 "2026-06-23T19:01:25Z")

</div>

I have this problem on a Synology DSM 918+. QNAP should NEVER have forced the higher encryption setting without giving us the option not to go to it. I am not sure Synology is going to upgrade the way they do rSync. It should be an option to move to the higher encryption AFTER you have verified the other end of your rSync relationships are in compliance.

Bad coder.

---

<div class="post-metadata">

**Author:** ![SysArmin](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@SysArmin](https://community.qnap.com/u/SysArmin)\
**Post date:** [July 4, 2026, 2:18pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/11 "2026-07-04T14:18:41Z")

</div>

Same here w/ QTS 5.2.9.3499

Backup fails to Synology NAS

Please fix this ASAP

---

<div class="post-metadata">

**Author:** ![Becker2020](https://avatars.discourse-cdn.com/v4/letter/b/ea5d25/32.png) [@Becker2020](https://community.qnap.com/u/Becker2020)\
**Post date:** [July 4, 2026, 3:52pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/12 "2026-07-04T15:52:27Z")

</div>

There is a new version

HBS 3 Hybrid Backup Sync 26.4.1.563 2026/07/02

[Fixed Issues]

- Fixed an issue where backup or sync jobs to Synology destinations could fail under certain firmware versions.

> **[Release Notes for Apps](https://www.qnap.com/en/app-release-notes?app=HybridBackup&product-line=nas)**
>
> QNAP designs and delivers high-quality network attached storage (NAS) and professional network video recorder (NVR) solutions to users from home, SOHO to small, medium businesses.

---

<div class="post-metadata">

**Author:** ![SysArmin](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@SysArmin](https://community.qnap.com/u/SysArmin)\
**Post date:** [July 16, 2026, 7:23am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/13 "2026-07-16T07:23:54Z")

</div>

It worked with the [version](https://www.qnap.com/en/app-release-notes?app=HybridBackup&product-line=nas) from 7/15/2026, thanks!

 ![temp](https://cdn-community.qnap.com/original/2X/2/22594cf44355f9a6e2d87b06ac8792a47a330b62.jpeg)

---

<div class="post-metadata">

**Author:** ![slc66](https://community.qnap.com/user_avatar/community.qnap.com/slc66/32/5511_2.png) [@slc66](https://community.qnap.com/u/slc66)\
**Post date:** [July 16, 2026, 11:56am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/14 "2026-07-16T11:56:00Z")

</div>

Hi,

As far as I’m concerned, the problem hasn’t been resolved in the latest version :  
HBS 3 Hybrid Backup Sync 26.4.2.617

Here is an example

`Erreur	2026-07-16	02:06:12	System	—	localhost	—	Hybrid Backup Sync	Custom Job Event	[Hybrid Backup Sync] Failed to complete Sync job: “DS-SLC_Documents”. Encountered error "kex_exchange_identification: read: Connection reset by peer`  
`" Check logs for more information.`

---

<div class="post-metadata">

**Author:** ![Becker2020](https://avatars.discourse-cdn.com/v4/letter/b/ea5d25/32.png) [@Becker2020](https://community.qnap.com/u/Becker2020)\
**Post date:** [July 20, 2026, 9:20pm UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/15 "2026-07-20T21:20:26Z")

</div>

There is a new version

HBS 3 Hybrid Backup Sync 26.4.3.647 2026/07/20

[Fixed Issues]

- Implemented security enhancements to improve application security.
- Fixed an issue where editing an S3 Compatible sync job could get stuck on “Loading” after upgrading from an older version.
- Fixed an authentication error that prevented connection to certain S3 Compatible storage services.

[Release Notes for Apps | QNAP](https://www.qnap.com/de-de/app-release-notes?app=HybridBackup&product-line=nas)

---

<div class="post-metadata">

**Author:** ![Becker2020](https://avatars.discourse-cdn.com/v4/letter/b/ea5d25/32.png) [@Becker2020](https://community.qnap.com/u/Becker2020)\
**Post date:** [August 12, 2026, 11:48am UTC](https://community.qnap.com/t/warning-connection-is-not-using-a-post-quantum-key-exchange-algorithm/6175/16 "2026-08-12T11:48:41Z")

</div>

There is a new version

HBS 3 Hybrid Backup Sync 26.4.4.788 2026/08/12

[Fixed Issues]

- Implemented security enhancements to improve application security.
- Fixed an issue where RTRR backup left temporary files in the destination NAS’s /tmp folder.
- Fixed an issue where RTRR backup jobs could fail with error when client-side encryption was enabled.
- Fixed an issue where deleted subfolders could reappear after a Two-way remote sync on certain models.

[Release Notes for Apps | QNAP](https://www.qnap.com/de-de/app-release-notes?app=HybridBackup&product-line=nas)
