Resolved "Internal error ;-P" when changing Apache web server settings from panel

[Bitpalast]

Plesk Onyx 17.5, CentOS 7.3, default installation, 64 Bit

When changing the Apache web server settings from the panel, a red error message is displayed:

Internal error ;-P
{"formMessages":{"apacheModules":{"apache_modules":{"notInArray":"This option is not supported."}}},"status":"success","statusMessages":[]}

 

[Bitpalast]

Answering my own question: This issue was caused by an error in domain and subscription tables / database inconsistencies after a domain name was added, removed, added removed within a few minutes. This seems to have messed up the domain table information and affected further changes to the database. After the domain/subscription error was resolved, Apache server configuration could be updated again without the error message.

 

[UFHH01]

*spam on*

Internal error ;-P

Did the Plesk Control Panel really show you it's tongue?

*spam off*

 

[Bitpalast]

It did indeed, it''s the authentic error message.

 

[Gus Papacharalampous]

Hello Peter,

I am getting the same error when trying to apply a change in the index.html. Any ideas?

 

[MarkM]

Try checking your Plesk database for inconsistencies.

# plesk repair db

 

[Gus Papacharalampous]

@Mark Muyskens I did but no error messages

 

[MarkM]

Did this possibly happen after the latest MU that came out yesterday? Maybe it's the actual installation and not just the DB....

# plesk repair installation

 

[MarkM]

Wait - I just noticed you're getting a CloudFlare error. Are you accessing Plesk thru a domain that traffic is running through Cloudflare? Try accessing Plesk using the IP and see if you can make edits that way...

 

[Bitpalast]

Mark, you're a wizard! You've pinpointed the issue.

 

[MarkM]

Atleast I did something productive at 4:20am local time ......

 

[Hex]

Wait - I just noticed you're getting a CloudFlare error. Are you accessing Plesk thru a domain that traffic is running through Cloudflare? Try accessing Plesk using the IP and see if you can make edits that way...

@Mark Muyskens I'm searching on the forum for this type of issues with Cloudflare for more than a week now and I found your answer similar to my case.

My Plesk is working thru Cloudflare and the only issue is this : on Plesk code editor for css or js files (When you click on these types of files the Plesk logout instantly, PHP and any other files are ok for editing (even .htaccess is ok for edit), what do you think?

Plesk onyx latest Version 17.8.11 Update #10, last updated on June 7, 2018 08:00 AM
CentOS7 AWS
Cloudflare Dev mode enabled - cach disabled - every possible option you can imagine - orange cloud enabled (if disabled no problems but what is the point of the service without security?)

My final search results are more proxy related issues with Cloudflare and Plesk server but I can't confirm that.

I can provide more info if you're interested.

 

[MarkM]

Maybe?

Plesk session is dropped if client’s IP changes

 

[Hex]

Maybe?

Plesk session is dropped if client’s IP changes

100%

I don't know why the css/js has it's own session on the editor with Cloudflare (maybe edge locations for passing these files) despite the Development mode turned on with no query string set.
+ that gives us an indication that Plesk is ready for most challenging scenarios on the market.

Thank you Mark for the hint.

 

[koentjha]

Hi There,
For some reason, Plesk is blocking (one of) the CloudFlare IP addresses.
Unblocking those IP addresses resolved my issues.

 

[Hex]

Hi There,
For some reason, Plesk is blocking (one of) the CloudFlare IP addresses.
Unblocking those IP addresses resolved my issues.

True, if you're talking about Obsidian. 18.20+
The Fail2ban block my own IP without much interaction with Plesk. Twice.
I'll do more tests to confirm and report the issue.