CONNECT_FAILED(35) to satellite server

[kjp1231]

I am trying to register an ASAv via my Satellite server but when I test the smart call home profile via CLI to my satellite server I get this message.

call-home test profile License

INFO: Sending test message to https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler...

ERROR: Failed: CONNECT_FAILED(35)

I can't find anything out about this message

[Walter Thompson]

Hi kjp1231,

What ver are you running?

Run the following debugs to help narrow the issue down and share the output here.

debug call-home smart-licensing all
debug license agent all
debug ip http client all

[Walter Thompson]

Scap the debug call-home smart-licensing all and instead use only debug call-home all.

[kjp1231]

I am running ASAv version 9.14(1) and satellite version 7-201907

I was able to 'debug call-home all' and 'debug license agent all' but the other debug commands didn't work.

Debug output shows - 

call-home test profile License

INFO: Sending test message to https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler...

ssh: processing test(Test) SCH Configuration Test

ssh: [0] dispatching test message to https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler

ssh: Dispatch to destination https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler

ssh: Opening dispatch channel: httpc/2/X.X.X.X/443/ssl/verify/sch//

ssh: Opened dispatch channel: httpc/2/X.X.X.X/443/ssl/verify/sch//

ssh: upload 2737 bytes

ERROR: Failed: CONNECT_FAILED(35)

R13-SDWAN-FW01# ssh: http request to https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler failed, rc -1

ssh: [0] Dispatch message(52) test to https://F.Q.D.N/Transportgateway/services/DeviceRequestHandler failed: CONNECT_FAILED(35)

[Roy Yuan]

@kjp1231, did you ever get this issue resolved?

[kjp1231 · Accepted solution]

Yes, support had me change to http instead of https. Don’t know why https wouldn’t work. I would think the preference would be https