Enabling HTTP/2 in Advisor extension does not work on Plesk server

Follow

Comments

11 comments

  • Avatar
    Barbara Muster

     Tried the work around.. but this also does not work :(

    Plesk keeps disabling http2 

     

    When will you fix this error?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Barbara, currently the exact ETA for the bug resolution is not available.

    However, as it is stated in the article, this is a cosmetic bug and can be safely ignored.

    0
    Comment actions Permalink
  • Avatar
    djyoungster32

    agree with Barbara Muster Plesk keeps disabling http2 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @djyoungster32, 

    What version of Advisor extension is used? The article is updated and the issue should have been resolved in version 1.3.0 of extension.

    0
    Comment actions Permalink
  • Avatar
    djyoungster32

    Advisor extension is Version: 1.3.2-178

    0
    Comment actions Permalink
  • Avatar
    Barbara Muster

    For me its Version: 1.3.2-178 

    0
    Comment actions Permalink
  • Avatar
    Alexandr Nikolaenko

    Hello @djyoungster32, @Barbara Muster,

    A have rechecked and clarified, that bug is still in work. A bugfix notification will be removed from the article in nearest future.

    Meanwhile, you can use provided workaround.

    0
    Comment actions Permalink
  • Avatar
    Lucaele

    Hi all,

    are there any news for this bug?

    Thanks!

    Luca

    0
    Comment actions Permalink
  • Avatar
    Ekaterina Babenko

    Hello Luca,

    Currently there is no ETA for bug fix.
    Information will be removed from Release notes shortly. I have already updated the article.

    Please, subscribe to it in order to be notified about bug fix.

    0
    Comment actions Permalink
  • Avatar
    Mitchell van Bijleveld

    Even though this is just a cosmetic bug, as a paid user I expect those small things to be fixed as soon as possible, and if the first reply to this bug is more than one year ago, I am very disappointed. 

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    @Mitchell

    Basically there are two reasons why it still not fixed:

    1. Bug is just cosmetic one and has no impact

    2. Bug occurs only with specific conditions and affect very small amount of users, those who have "ssl.protocols" configured in panel.ini

    That's why it has "low" priority. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request