topic "CRLs failed to be downloaded" error when access SmartConsole R80.30 in General Topics

"CRLs failed to be downloaded" error when access SmartConsole R80.30

Chinmaya_Naik — Tue, 14 Jul 2020 18:23:59 GMT

Dear Checkmates,

I am unable to access the smart console from specific IP eg:x.x.x.x

Find the below details that I checked.

1) GUI client define : any
2) Host access : any
3) Smartconsole Trusted Client : any
4) Reboot the problematic Machine
5) Installed the new updated smartconsole in the problematic machine (Build 90)
6) 18246 , 18190 and 19009 port also listening from the server.
7) Run the smartconsole as "Run as Administrator"
8)Check the connectivity able to take ssh and webui.
9) Add manually assigned IP address x.x.x.x in GUI Client but not working
10) Add manually assign the host access IP address x.x.x.x but not working
11) Changed the IP address to y.y.y.y and able to access the mgmt smartconsole
12) Changed the IP address to x.x.x.x and able to access the Different Mgmt smartconsole.
13) No logs found in messages file.

Kindly suggest any solution expect Debug if any ?

Regards

@Chinmaya_Naik

Re: "CRLs failed to be downloaded" error when access SmartConsole R80.30

Wolfgang — Tue, 14 Jul 2020 19:54:00 GMT

Anything checked from "CRLs failed to be downloaded" error in SmartConsole when trying to connect to Management Server / SmartEvent Server ?
The needed ports are accessible from host running smartconsole ?

Wolfgang

Re: "CRLs failed to be downloaded" error when access SmartConsole R80.30

Chinmaya_Naik — Thu, 30 Jul 2020 17:15:41 GMT

Issue is resolved now , its just a communication issue.

Re: "CRLs failed to be downloaded" error when access SmartConsole R80.30

RAVISH — Sat, 26 Jun 2021 11:07:06 GMT

HI ,

Can you let me know what connectivity issue you had ?Actually I am also facing same issue and did same process as you mentioned in starting troubleshooting .Please revert ASAP

Re: "CRLs failed to be downloaded" error when access SmartConsole R80.30

the_rock — Sun, 27 Jun 2021 15:37:26 GMT

Wolfgang provided excellent sk for that, as 99% of the time, that type of error would indicate communication issue.

Cheers.