• 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 Monitoring extension: you can install the Monitoring extension even when Nginx is not installed on the server

Maarten

Golden Pleskian
Plesk Guru
Username:

TITLE

Monitoring extension: you can install the Monitoring extension even when Nginx is not installed on the server

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.42 Update #1

PROBLEM DESCRIPTION

I've seen a couple of threads on this forum from users that install the Monitoring extension on a Plesk server without Nginx. This results in a non-working extension with a warning "origin not allowed".

The extension should check if Nginx is running before it gets installed.

STEPS TO REPRODUCE

- remove Nginx from the server
- install the Monitoring extension
- Open the Monitoring extension and you'll see empty graphs with a warning: "origin not allowed"

ACTUAL RESULT

When you open the Monitoring extension you'll see empty graphs with a warning: "origin not allowed"

EXPECTED RESULT

Working graphs without the warning.

ANY ADDITIONAL INFORMATION

The extension should check if Nginx is running before it gets installed. If not, it should not continue the installation.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for the report.
The bug was confirmed and submitted as EXTPLESK-3426
 
BTW, Temporary workaround here:

1 step. To the template

/usr/local/psa/admin/conf/templates/default/server/apachePleskAccess.php

to the section

<IfModule mod_proxy_http.c>
<Location />
ProxyPass http://127.0.0.1:8880/
ProxyPassReverse http://127.0.0.1:8880/
RequestHeader set "X-Forwarded-Proto" "https"
Order allow,deny
Allow from all
</Location>

add the following line

ProxyPreserveHost On

and re-disable nginx proxy via `plesk sbin nginxmng -d`.

OR

you can modify the

/etc/apache2/plesk.conf.d/server.conf

file with the same way and restart apache2 via `service apache2 restart`.

2 step. Modify

/etc/sw-cp-server/conf.d/grafana_plesk.inc

replace

rewrite ^/modules/grafana/service/login$ /modules/grafana/service/login/generic_oauth redirect;

with

set $r_scheme $scheme;
if ($http_x_forwarded_proto = 'https') {
set $r_scheme https;
}
rewrite ^/modules/grafana/service/login$ $r_scheme://$http_host/modules
 
Back
Top