Web Smartconsole with fqdn

[Roy_Smith]

Hi

We have just upgraded our MDS servers from R80.40 to R81.10, without any problems. I'm now looking at Web SmartConsole to compare it with the SmartConsole app and with a view to roll it out to some of our admins. 

If I access Web SmartConsole using https://<IP Address>/smartconsole I am able to authenticate successfully and access smartconsole fine. However, if I use a FQDN instead of the IP address, i.e. https://servername.domain/smartconsole, I am unable to authenticate and it returns the message "Authentication to server failed".

I am able to use the FQDN to access the GAIA portal and smartview. I can still use the Smartconsole app with no issues. It is just web SmartConsole with a FQDN that gives me a problem.

I have to assume that using a FQDN is supported? Has anyone else come across this issue? Any ideas to resolve it?

Many thanks
Roy 

[the_rock]

Hm, thats very interesting...lets see if someone from CP can confirm. Clearly, resolving works fine if you access dashboard itself using fqdn, its possible it might not be fully supported using web smart console.

[PhoneBoy]

May be a limitation, but probably need a TAC case to confirm it’s not a bug.

[Ofir_Calif]

Hi @Roy_Smith,

We are aware of this issue and working to resolve it.

Thanks,
Ofir.

[Roy_Smith]

Ofir

That's good to know, thanks.

Roy

[pf]

Hi Ofir,

any news on that? We need to pass the Web SmartConsole through a reverse proxy and are facing the same issue. Would be nice if you can share details about this issue so maybe we can fix it on our reverse proxy.

thanks,

Patrick

[tto]

Hi @Ofir_Calif,

I would be very interested in an update on this issue. Can we configure aliases or domains to connect to the Smartconsole?

Thanks,

Torge

[Ofir_Calif · Accepted solution]

Hi,

the issue is fixed in R81.10 jumbo take 79.

note that the FQDN is capable to be resolved on the MGMT server.

Thanks,

Ofir.

[S_E_]

hi,

It looks like that there was an autoupdate of the web smartconsole.

Web SmartConsole Post Install finished successfully
*N* %03-06 09:37:58% : Script /var/log/AutoUpdater/metadata/mwc/web_console/webconsole_AutoUpdate/76/product_scripts/CheckHealth.sh output:

start Web SmartConsole - CheckHealth
Mon Mar 6 09:37:58 GMT 2023

However, login does not work anymore.

Authentication works when using https://<IP>/smartconsole instead https://<FQDN>/smartconsole.

I can see the domains. But when I select a domain it ends up with 'Unable to connect to server". 

[Expert@MDS:0]# cpinfo -y all
This is Check Point CPinfo Build 914000227 for GAIA
[MGMT]
HOTFIX_R81_10_JUMBO_HF_MAIN Take: 78

BUNDLE_WEBCONSOLE_AUTOUPDATE Take: 76

sk173968 does not help

b.t.w. Client is inside 'trusted clients'. Any tips what I should check?

Regards

[PhoneBoy]

This might require a TAC case.
At the very least, I believe they can help you revert to the previous version.

[Ofir_Calif]

Hi @S_E_ ,

we are looking into it, and will update soon.

Thanks,

Ofir.

[Ofir_Calif]

Hi @S_E_ ,

we did not manage to replicate it.
please open a TAC case so we can assist you.

Thanks,

Ofir.

[the_rock]

I will try replicate this in R81.20 lab and let you know the results.

[akkouadio3]

Hello,

I have the same error, but I don't know if the error is due to the fact that I'm using AD authentication for the connection.
The browser doesn't open the new window to connect to the CMA and I get the message "failed to connect to the server".

Version: R81.10 take 94

Web smarconsole version 90

[A_KOUADIO]

Hello,

I have the same error, but I don't know if the error is due to the fact that I'm using AD authentication for the connection.
The browser doesn't open the new window to connect to the CMA and I get the message "failed to connect to the server".

version : R81.10 TAKE 94

WEB SMARTCONSOLE TAKE 90

[the_rock]

You get that on every CMA or just one?

Andy

[A_KOUADIO]

ALL

[the_rock]

Maybe check with TAC.

Andy

[A_KOUADIO]

Does this work in your case with AD authentication?

[Krups]

Hi,

We are in 81.10 take 110 and we have the same problem.

The Web Smart console is working well with IP but not with the FQDN. We have an "Authentication to server failed".