Issue Cannot read properties of null (reading 'id')

[brhospedagem]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

18.0.63 #1

When trying to access a client's control panel, the error below appears. This only happens to some clients, and started on August 7, 2024.


What should we do to fix the problem?

Thank you!


TypeError: Cannot read properties of null (reading 'id')
at https://br01.brhospedagem.com.br:84.../smb/web/view.js?63e47ba77db638d41f19:7:27163
at Object.useMemo (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:69078)
at t.useMemo (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:12:6045)
at SiteCard (https://br01.brhospedagem.com.br:84.../smb/web/view.js?63e47ba77db638d41f19:7:27123)
at Cl (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:62770)
at ko (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:119279)
at yc (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:108527)
at bc (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:108455)
at vc (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:108318)
at cc (https://br01.brhospedagem.com.br:8443/ui-library/plesk-ui-library.min.js?1723201136:35:105480)

 

[Sebahat.hadzhi]

Hello, @brhospedagem. We are sorry to hear about the issue you are experiencing after the update. In order to get a better idea of what might be leading to it could you please look into the Plesk panel log file for possible errors and share the output for the recent entries:

cat /var/log/plesk/panel.log | grep ERR

Thank you in advance for your cooperation.

 

[Bitpalast]

As the error indicates a JavaScript issue, it might be caused by cached data. Clearing the browser cache could be enough to solve it.

 

[counterweightmedia]

I am currently having this same issue - saw the other post that it was solved? I am not sure I understand how it was solved. @brhospedagem