[FIXED BUG] Mixed-case domains do not work on PHP-FPM by Apache: 503 service unavailable

Follow

Comments

6 comments

  • Avatar
    DynamicHosting

    Step 3 should say Domains > testExample.com -> Hosting Settings: example.com, since it is renaming a test name to the correct final lower-case domain name.

    0
    Comment actions Permalink
  • Avatar
    Alexey Lapshin

    Hello DynamicHosting,

    Thank you for pointing out attention to this. The article updated.

    0
    Comment actions Permalink
  • Avatar
    DynamicHosting

    Thanks Alexey, but the final "Example.Com" should read "example.com" otherwise you will still have a mixed-case final domain name.

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    Hi DynamicHosting,

    According to the internal documentation and discussion about this bug, it's not needed to rename the domain to lower-case.

    I mean, renaming the domain to lower-case will eliminate completely the issue, as no capital letters will be in the name, so the bug won't apply.

    The last rename is set to include Capital Letters to continue being as it was at the beginning, to keep the capital letters but re-generating the ASCII naming properly.

    I hope now it's more clear.

    0
    Comment actions Permalink
  • Avatar
    Detlef Bracker (Edited )

    Is somebody in the Plesk company know, what they are doing? 

    A) This problem about mixed letters, I have reported many years ago and it comes every time back !!!
    B) A renaming of Domain-Name as in this article as bug fix is written, is not possible, why Plesk in this last and in the newest version not accepted this - when you change the letters and click the save button, then you get: "Dieser Domainname existiert bereits." (translated: this domainname exitsts equal) !!!
    C) In the discription of this article in april 16 francisco garcia write "According to the internal documentation and discussion about this bug, it's not needed to rename the domain to lower-case." but Marc Lopez write 2 days ago, (so must been the 29.07.2020 why we have today the 31.07.2020 or when the date is other, then its a plesk webpage bug - not a feature) !!!!
    D) The updater - I must start today on one machine and I get the warning: 'WARNING: Found one or more domains with mixed case names. Such domains may have trouble working with the "FPM application server by Apache" handler.'

    Please can now cleared on highest chef level, what is wrong or what will hold plesk as a feature to get more money for support tickets from customers?

    Why this horror must please end!

    Regards

    Detlef

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia (Edited )

    Hi Detlef Bracker,

    In general, I agree that not all the information was properly explained here, plus let me answer point per point:

    A) This problem about mixed letters, I have reported many years ago and it comes every time back !!!

    Yes, I know this is long-running issue, and now we know it's a bug in Apache version lower than 2.4.14:

    https://bz.apache.org/bugzilla/show_bug.cgi?id=57968
    https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES

    Anyway, also Plesk was improved in a way to avoid the bug in lower versions of Apache, for example: in my test server with Plesk Obsidian 18.0.29.0, CentOS 7.8.2003 and Apache/2.4.6 (with PHP 7.4 as FPM served by Apache), it's not malfunctioning and Wordpress of T3sT.com works fine.

     

    B) A renaming of Domain-Name as in this article as bug fix is written, is not possible, why Plesk in this last and in the newest version not accepted this - when you change the letters and click the save button, then you get: "Dieser Domainname existiert bereits." (translated: this domainname exitsts equal) !!!

    Such message is being shown when trying to rename T3sT.com to t3st.com (from mix to lower letters only), unlike what is explained in the article itself where you must set it like from T3sT.com to newT3sT.com, and then back to T3sT.com.

    Are you sure you're following the right procedure?

     

    C) In the discription of this article in april 16 francisco garcia write "According to the internal documentation and discussion about this bug, it's not needed to rename the domain to lower-case." but Marc Lopez write 2 days ago, (so must been the 29.07.2020 why we have today the 31.07.2020 or when the date is other, then its a plesk webpage bug - not a feature) !!!!

    Please, don't take my words from 16th of April out of context. Such words are an answer exclusively to April 13 comment. Not about the article itself.

    Those are different topics, and sections. Upper is the article itself, and then below the comments box.

    In addition to that, I would say that the right procedure (and in my own opinion), it would be better to avoid using capital letters on domains and do like so:

         T3sT.com -> newt3st.com > t3st.com

     

    D) The updater - I must start today on one machine and I get the warning: 'WARNING: Found one or more domains with mixed case names. Such domains may have trouble working with the "FPM application server by Apache" handler.'

    Yes, this is meant to make you aware of such existing bug and to take action in case you find issues with existing domains, as the article says. But only once the Plesk was upgraded to Obsidian.

     

    Moreover, please note that I've updated the article accordingly.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request