How to enable the Apache server statistics on a Plesk server

Follow

Comments

10 comments

  • Avatar
    Karl May

    CentOS 7: /etc/httpd/conf.modules.d/status.conf file not exists on CentOS 7.5.1804

    I have result "status_module (shared)" and apache 2.4.6 (CentOS)

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hi @Karl,

    As written at the step 4, create etc/httpd/conf.modules.d/status.conf in case the file does not exist.

    That is ok for a default installation.

    0
    Comment actions Permalink
  • Avatar
    Sharul Hafiz

    Tried this and it doesn't work. Also tried putting require all granted in case I put the wrong IP but still doesn't work.

    0
    Comment actions Permalink
  • Avatar
    Anna Morozyuk

    Hi @Sharul Hafiz,

    It's quite tricky to conclude here what can cause this, so to sort it out, please contact support: How to submit a request to Plesk support?

    0
    Comment actions Permalink
  • Avatar
    Bob B (Edited )

    I use CentOS 7.6 with Apache 2.4.  The above instructions to create "/etc/httpd/conf.modules.d/status.conf" do not work. 

    I noticed that there is a "status.conf" already existing in "/etc/httpd/conf.d" with the following contents:

    ExtendedStatus on
    <Location /server-status>
    SetHandler server-status
    Order deny,allow
    Deny from all
    Allow from 127.0.0.1
    </Location>

    If I add another "Allow from x.x.x.x" line, where "x.x.x.x" is my IP address, it works.

    Given this information, please review and advise of preferred method to enable server-status on CentOS 7.6 with Apache 2.4.

    Thanks!

     

    Update:

    I settled on the following configuration, in /etc/httpd/conf.d/status.conf, which allow access by IP, or password:

    ExtendedStatus on
    <Location /server-status>
    SetHandler server-status
    AuthType basic
    AuthName "Apache status"
    AuthUserFile /etc/httpd/conf/server-status_htpasswd
    <RequireAny>
    Require valid-user
    Require ip x.x.x.x
    Require ip 127.0.0.1
    </RequireAny>
    # Order deny,allow
    # Deny from all
    # Allow from 127.0.0.1
    # Allow from x.x.x.x
    </Location>

    Please advise if there is a better way to do this.

    0
    Comment actions Permalink
  • Avatar
    Konstantin Annikov (Edited )

    @Bob B

    Thank you for the feedback. 

    I created fresh VM with CentOS 7.6 base installation, Apache 2.4 and Plesk Onyx: 

    # plesk version | grep Product.
    Product version: Plesk Onyx 17.8.11 Update #48
    # httpd -v | grep version
    Server version: Apache/2.4.6 (CentOS)
    # cat /etc/centos-release
    CentOS Linux release 7.6.1810 (Core)

    And I could not see "status.conf" file in "/etc/httpd/conf.d" directory. I believe that file on your server has been created manually earlier. And our guide is compatible for CentOS 7.6 and Apache 2.4.
    As for your configuration, it is fully correct. hope that other pleskians will also find your snippets useful.

    0
    Comment actions Permalink
  • Avatar
    Bob B

    @Konstantin, Thanks!  This is a fresh and new server.  Perhaps my dedicated server provider made customizations.  Alternatively, maybe enabling Plesk's Health Monitor or Watchdog or some other extension, could have added that file.

    0
    Comment actions Permalink
  • Avatar
    Konstantin Annikov

    @Bob B, 

    I also suppose that server provider could make some customizations in server's template. Moreover, I have installed all the components in Plesk installer, however config file still does not exist in conf.d. 

    0
    Comment actions Permalink
  • Avatar
    Thomas Seifert

    With Plesk 17.8.11 update 67 on CentOS Linux release 7.6.1810 (Core) with Apache/2.4.6 (CentOS) the Apache-Status site will not work when the status.conf file is placed in the "/etc/httpd/conf.modules.d/status.conf" directory.

    I have to put the status.conf file in the "/etc/httpd/conf.d/status.conf" directory to get it worked.

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    Hello @Thomas Seifert,

    Thank you for your input.

    I tried to reproduce the issue on my side, however, it works as expected with /etc/httpd/conf.modules.d/status.conf.

    To investigate the cause of such behavior, please contact Plesk Technical Support: How to submit a request to Plesk support?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request