# Rocky 9.1 SSH login issue in FIPS mode **URL:** \ **Category:** Social & Community\ **Created:** [December 23, 2022, 4:55pm UTC](https://forums.rockylinux.org/t/rocky-9-1-ssh-login-issue-in-fips-mode/8347 "2022-12-23T16:55:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![srakow](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@srakow](https://forums.rockylinux.org/u/srakow)\ **Post date:** [December 23, 2022, 4:55pm UTC](https://forums.rockylinux.org/t/rocky-9-1-ssh-login-issue-in-fips-mode/8347/1 "2022-12-23T16:55:16Z")
I am currently working on building a test environment in FIPS mode and having issues doing an SSH into the box. From PuTTY I get “Remote side unexpectedly closed network connection” From a 9.1 box to 9.1 box, the messages are: “kex\_gen\_client: Key exchange type c25519 is not allowed in FIPS mode” “ssh\_dispatch\_run\_fatal: Connection to IP\_ADDRESS port 22: invalid argument” I have found where there are issues going back to RHEL 6, but I would think that would not be an issue between Rocky 8 or 9. I have tried the fixes that they have put out for RHEL 6 without success. Has anyone else found this issue? Scott ---
**Author:** ![srakow](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@srakow](https://forums.rockylinux.org/u/srakow)\ **Post date:** [December 23, 2022, 8:43pm UTC](https://forums.rockylinux.org/t/rocky-9-1-ssh-login-issue-in-fips-mode/8347/2 "2022-12-23T20:43:46Z")
So I have found a work-around for this. I removed all references to 25519 in the /etc/crypto-policies/back-ends directory. There are soft links for most of the files in the /usr/share/crypto-policies/DEFAULT directory. After a reboot the ssh connection was made from both PuTTY and another server. Scott ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\ **Post date:** [August 25, 2023, 3:30am UTC](https://forums.rockylinux.org/t/rocky-9-1-ssh-login-issue-in-fips-mode/8347/3 "2023-08-25T03:30:09Z")