No supported authentication methods available (server sent: publickey)

[genisis__]

Just faced an interesting connectivity issue when installing JHFA61.  

Issue:
After entering username when connecting via SSH, we see the message
"No supported authentication methods available (server sent: publickey)"

Resolution:
clish
set ssh server password-authentication yes
save config

Please note this may happen on an existing appliance where you have uninstalled an old jumbo and then installed JHFA61.

When doing a clean build with R81.10 and then installing JHFA61 I did not experience this issue.

TAC are aware.

[MatanYanay]

Hi @genisis__ 

Thanks for your feedback 

We are aware of the SSH issue and we are working to release a fix for this issue in the upcoming days 

Thanks

Matan.

[the_rock]

Thanks for posting this, super useful!

[Chris_Atkinson]

JHF T66 would seem to include a related fix, please advise if your issue persists?

[genisis__]

Can we confirm that only two changes have actually been included in JHFA66 and if so does this mean it will go to GA shortly considering JHA61 almost hit one month in ongoing status.

[MatanYanay]

Hi @genisis__ 

indeed our target is to have short ongoing time for Take T66 as we already have 1 month converge of Take 61

we will monitor our systems with this take and I hope we will be able to declare it as GA in 1-2 weeks time  

Thanks 

Matan.

[genisis__]

Thanks for the update.

Installed JHFA66, no issues to report thus far.

[Lloic]

Hello,
We are facing this issue on a 6200P Firewall on a site, with T87 and even with T94, we have the ssh accept "no supported authentication..Pub key", HTTPS is forbidden.
Does someone have an idea ? I'm submitting a ticket to CKP.

[genisis__]

Did you check the solution I posted at the top of this thread? 

It sounds like the same problem I had, if so, follow the procedure about, if this works report to TAC as it clearly means this is broken again.

[Lloic]

Yes with a console cable we access to the config, restart the SSH but it's more like a workaround to get an temporary access, we still need to restore HTTPS access and have the normal behavior. Let's see what we can get from Checkpoint.
Thanks !

Tested on R81.10  - R81.10 T87 - R81.10 T94, same results.