• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Forwarded to devs Wrong SERVER_PORT values

Mattia_98

New Pleskian
TITLE:
Wrong SERVER_PORT values
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.8.11, Debian 8 x86_64
PROBLEM DESCRIPTION:
Since some time we have noticed that some of our websites stopped working. We have applied a workaround to make them work again but some have been inaccessible for a day and more. Now we have noticed that whenever we change a configuration the website stops working. We have identified the change that causes the websites to stop working. On the websites that do not (yet) require the workaround, the SERVER_PORT variable is correctly set to either 80 or 443. The security feature of our CMS (Typo3) does not trigger and the website works normally. Whenever now something triggers the regeneration of the configuration files, the SERVER_PORT variable is set to either 7080 or 7081. This causes the security features of the CMS to trigger and not allow anyone the access the website. We therefore have to temporarily disable them.
I assume this bug is caused by a recent update and I urge the Plesk team to take a look at it before more of our websites become inaccessible without us noticing.
Thank you very much​
STEPS TO REPRODUCE:
Change any configuration that triggers a regeneration of the configuration files.​
ACTUAL RESULT:
The site stops working.​
EXPECTED RESULT:
The site continues working.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
From Developer:

I've installed Typo3 at our test environment and everything works as expected. What version of Typo3 is a customer using?

the security features of the CMS to trigger and not allow anyone the access the website

What exactly the security feature of the CMS was mentioned?
Need more info or credentials to customer's server for the further investigation.
 
Back
Top