Server error : No ECDSA host key is known for netadmin2.intra.chu-rennes.fr . Host key verification failed.

[Mamoudou]

Hello team,

I have a problem with my export configuration Panorama via  scheduled task.

When I make a test SCP server connexion I have this mesage : 

Before upgrade to 10.2 the export was working fine.

I have also saw that PAN-188052 talk about this issue. Do you know how to fix it ? 

Could you help me please tu understand this problem.

Thank you in advance.

[JanneKing]

Hi, upgraded to 10.2.4 and I can confirm they haven't fixed this. For me, backing up is important so I can't understand why this is such a low priority?

[Mamoudou]

Hello,

I have the same problem. I havea session with the TAC to fix the issue and this is ths second time.

I will ask them a real solution for this problem because we didn't need to contact them every time.

[Mamoudou]

I resolved again with session with TAC who has connected as root to make some change.

I asked them when this issue will be fix definitively, they said me there is a workaround in progress.

[David-P]

Upgraded to 10.2.4.h2 from 10.1.10 and now have this issue. not fixed in 10.2.4 h2 for panorama.

[Toivo]

We're seeing the same issue appear after updating from 10.1.x to 10.2.4-h2 😞

[Tobi]

PAN-OS 10.2.4-h3 finally worked for me.

PAN-218620

Fixed an issue where scheduled configuration exports and SCP server connection testing failed.

[pbezouska]

Still have the issue on 10.2.5 and 10.2.6. **bleep** it Palo

[miguelMA]

hello all,

since replying to this issue, i've changed what i do.

in panorama,

device registration auth key

i now choose device type FIREWALL instead of "any"

since doing this, have not seen this issue come up again, also, we are running pannorama 11.0.2 and 10.2.3 h2 or higher on the fw's.

hope this helps.

[tkim_confluent]

Can you elaborate how this would fix the issue? After creating registration auth key, do i try scp panorama configration using Scheduled Config Export.

[miguelMA]

if the issue is already occuring, only thing i have found that fixes is tac login into it and root access...however when adding new fw's i now create a device registration key and instead of the drop option default setting of "any" i drop down the menu and choose "firewall"

and this seems to avoid the issue altogether...can't explain it but have not had this issue at all, usting this steps.