You also missed: -Enable the SSL module: sudo a2enmod ssl sudo a2enmod rewrite -disable the default config with: sudo a2dissite 000-default.conf -The config files should be vhost_prtg_ssl.conf and vhost_prtg.conf, respectively. This in order to be compliant with the Apache config file modularity. -Then enable both site configs with: sudo a2ensite vhost_prtg_ssl sudo a2ensite vhost_prtg sudo service apache2 reload (with this you can skip the part: Then either create a symbolic link ("ln -s source target") in your sites-enabled directory for the just created files or just copy them over from sites-enabled.)

Can I use Apache as reverseproxy to handle PRTG as context?

https://mydomain.com/prtg -> http://myprtgserver

Best Regards Christian

Hello Christian,
please excuse the delay in our reply.

I was informed by the article's author that this is currently not possible due to the way PRTG internally handles links.

Best Regards,
Luciano Lingnau [Paessler Support]

Hello

Is it possible to use SSL between apache and PRTG? Otherwise all passwords are transfered in plaintext between the proxy and the PRTG webserver.

We use the SSL proxy to acces the webserver from the internet (for app without VPN).

Cheers

Dear vps,

I don't know about Apache's side, but PRTG can use HTTPS. This can be configured in the PRTG Administration Tool.

Hello

I figured out how to use an apache as a reverse proxy for PRTG while still being able to use internal HTTPS certificate:

<IfModule mod_ssl.c> <VirtualHost *:443> ServerName YOUR_SERVER.COM DocumentRoot /var/www/html

ErrorLog ${APACHE_LOG_DIR}/error.log

1. Possible values include: debug, info, notice, warn, error, crit,
2. alert, emerg. LogLevel warn

CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined SSLEngine on

1. Adjust the following two lines to use your own certificate (lets encrypt works fine) SSLCertificateFile /etc/letsencrypt/live/cert.pem SSLCertificateKeyFile /etc/letsencrypt/live/privkey.pem

SSLProxyEngine on SSLProxyVerify none SSLProxyCheckPeerCN off SSLProxyCheckPeerName off

1. Adjust following two lines according to your infrastructure ProxyPass / "https://INTERNAL_IP_OR_DNSNAME:443/" ProxyPassReverse / "https://EXTERNAL_IP_OR_DNSNAME:443/"

</VirtualHost> </IfModule>

due to this Information is at least 3 years old, I would like to do some follow up..

here is my vhost config for prtg:

## monitoring\\ <VirtualHost *:80>\\ ServerName monitoring.domain.com\\ RewriteEngine on\\ RewriteCond %{HTTPS} !=on\\ RewriteRule ^/?(.*)$ https://%{SERVER_NAME}/$1 [R,L]\\ </VirtualHost>\\ \\ ## SSL_monitoring.domain.com\\ <VirtualHost *:443>\\ SSLEngine on\\ SSLProxyCheckPeerCN off\\ SSLProxyCheckPeerName off\\ SSLCertificateFile /_CERT/fullchain.pem\\ SSLCertificateKeyFile /_CERT/privkey.pem\\ SSLProxyVerify none\\ ProxyPreserveHost On\\ Protocols h2 http/1.1\\ Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"\\ ServerName monitoring.domain.com\\ <Proxy *:443>\\ Order allow,deny\\ Allow from all\\ </Proxy>\\ SSLProxyEngine on\\ ProxyPass / http://10.1.1.6:80/ retry=3 timeout=3000\\ ProxyPassReverse / http://10.1.1.6:80/\\ ErrorLog ${APACHE_LOG_DIR}/monitoring.domain.com.log\\ CustomLog ${APACHE_LOG_DIR}/monitoring.domain.com.log combined\\ </VirtualHost>

and this is my vhost ssl settings:

SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1\\ SSLHonorCipherOrder off\\ SSLSessionTickets off\\ SSLUseStapling On\\ SSLStaplingCache "shmcb:logs/ssl_stapling(32768)"\\

Settings on prtg:
- no ssl
- port 80

my apache version is:
Apache/2.4.38 (Debian)

It seems that everything is working, but accessing from outside, the devices are not showing up. The devices tab is completely empty.

also tested nginx - facing same issue.

anyone facing similar problems?

Yaya,

Are you logging into PRTG as an administrator account? Can you try logging into it with an incognito tab?

Benjamin Day
[Paessler Support]