Issue PHP settings won't open

[Julian Nieborg]

Since today one of our Plesk servers won't open the PHP settings in the hosting tab.
If I click on the PHP settings tab it does nothing and if I reload the page it only shows a white page.

This is only happening on one of our server that has the same update treatment as all the other servers.

Does anyone has a Solution for this?

Thanks

 

[Bitpalast]

There are basically three things you can try:
a) Check /var/log/plesk/panel.log file for further details. Maybe an error is logged.
b) Use a different browser, preferrably on a different machine, to exclude browser issues.
c) Clear the cache of the current browser, also check whether it is using antivirus plugins. Some of such plugins frequently interfere with websites, specificially with JavaScript components. McAfee Web Advisor for example is known for this.

 

[Julian Nieborg]

Hi Peter,
Thanx for the reply!


A) This is the error log after I load the PHP settings panel:

[2022-03-22 13:43:01.031] 8058:6239c45507933 ERR [panel] Instance # does not exist
[2022-03-22 13:43:02.195] 284335:6239c4562f9ff ERR [panel] Instance # does not exist
[2022-03-22 13:43:05.021] 284335:6239c45905264 ERR [panel] Instance # does not exist
[2022-03-22 13:43:06.118] 40822:6239c45a1cd68 ERR [panel] Instance # does not exist
[2022-03-22 13:43:07.907] 8058:6239c45bdd572 ERR [panel] Instance # does not exist
[2022-03-22 13:43:08.879] 8059:6239c45cd6ad8 ERR [panel] Instance # does not exist
[2022-03-22 13:43:11.158] 40822:6239c45f268cf ERR [panel] Instance # does not exist
[2022-03-22 13:43:12.108] 57846:6239c4601a620 ERR [panel] Instance # does not exist

B) I've already tried that, but no results. Al my clients experience the same.
C) Same as B

 

[Bitpalast]

"Instance # does not exist": In this situation I'd probably start with a database repair:
# plesk repair db -y
The page might not load, because it requires objects that are not associated with the whole subscription and domain structure correctly.

 

[Julian Nieborg]

Still the same.

It showed some warnings and repaired the tables.
I've restarted Plesk.
Same errors in the log.

 

[Maarten.]

Do you get any errors in the browser console log?

In Firefox:
- Right click on the page
- Click on "Inspect"
- Click on the "Console" tab

 

[Julian Nieborg]

Yes, i get:

Uncaught (in promise) SyntaxError: Unexpected token < in JSON at position 0
Promise.catch (async)
(anonymous) @ Routes.js:63
(anonymous) @ Routes.js:76
oo @ react-dom.production.min.js:211
ki @ react-dom.production.min.js:257
t.unstable_runWithPriority @ scheduler.production.min.js:19
qa @ react-dom.production.min.js:122
_i @ react-dom.production.min.js:257
(anonymous) @ react-dom.production.min.js:256
D @ scheduler.production.min.js:17
w.port1.onmessage @ scheduler.production.min.js:14

 

[Maarten.]

That's what I expected: Plesk uses React on the backend and you are getting an React error.

One of the Plesk dev's should take a look I guess.

 

[Maarten.]

Just to be sure:
Have you tried to disable the browser plugins that do stuff with Javascript like: uBlock Origin, Privacy Badger, Ad Blocker etc?

 

[Julian Nieborg]

Yes disabled all my browser plugins, I've even tried it in a Windows sandbox.

 

[Maarten.]

I would suggest you contact the Plesk Support Team and refer to this thread.

Submit a request – Plesk Help Center

support.plesk.com