• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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