hi @gsmith!
Thanks for your response!
Yes, we’re running through apache2, configured like this:
<VirtualHost *:443>
ServerName gl.FQDN.com
DocumentRoot /var/www/html
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<Location />
RequestHeader set X-Graylog-Server-URL "https://gl.FQDN.com/"
ProxyPass http://127.0.0.1:9000/
ProxyPassReverse http://127.0.0.1:9000/
</Location>
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/graylog-error.log
CustomLog ${APACHE_LOG_DIR}/graylog-access.log combined
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
SSLCertificateFile /etc/ssl/apache2/cert.pem
SSLCertificateKeyFile /etc/ssl/apache2/key.pem
SSLCertificateChainFile /etc/ssl/apache2/fullchain.pem
</VirtualHost>
The ssl certificate is valid, and since the whole of graylog works perfectly, I didn’t think of including the apache config. Sorry.
It is just this paticular notification under “Alerts” that is causing the server.log errors, and that I cannot delete. I created and deleted a new test notification, just to make sure that there is no bigger global issue.
It seems some kind of corruption exists with this particular notification, and as I no longer need it, simply getting rid of i would be fine. But how…?
Let me know if there is anything else needed…?
Thanks again!