Log Server no longer accepting smartview access

[P_Williams]

Hi,

We recently upgraded our log server to R82 hotfix 122 from take 44 and since then I am unable to log into the web gui for smartview. I use the web gui to run monthly reports. I can access the logs via smartconsole without issue.

# api status

API Settings:
---------------------
Accessibility: Require local
Automatic Start: Enabled

Processes:

Name State PID More Information
-------------------------------------------------
API Started 6793
CPM Started 6793 Check Point Security Management Server is running and ready
FWM Started 11452
APACHE Started 10406

Port Details:
-------------------
JETTY Internal Port: 57384
JETTY Documentation Internal Port: 52960
APACHE Gaia Port: 443

Profile:
-------------------
Machine profile: 24800-35800 with SME
CPM heap size: 3072m

Apache port retrieved from: dbget http:ssl_port

--------------------------------------------
Overall API Status: Started
--------------------------------------------

API readiness test SUCCESSFUL. The server is up and ready to receive connections

Notes:
------------
To collect troubleshooting data, please run 'api status -s <comment>'

Any ideas what I can do to get it working again?

[PhoneBoy]

That's general API status, not specific to SmartView, which has other components.
What specifically occurs when you attempt to access SmartView? (screen shot, error messages, etc)
Have you opened a TAC case on this?

[P_Williams]

There is an attached image with the error, it is a 403 Forbidden error.

Forbidden

You don't have permission to access this resource.

We do have support through some 3rd party but right now I dont have access to their portal to log a ticket so I thought I'd try to fix through here in the mean time.

[PhoneBoy]

Missed that, my bad.
According to sk167092, it suggests that you configured a "Trusted Client" with only a hostname, not an FQDN.
Configure the Trusted Clients in SmartConsole using their FQDN (example: hostname.domain.xyz) and publish the session.

[emmap]

Is DNS resolution working from the log server? Are your allowed client settings ok? Maybe Install Database to the log server?