# HTTPS signature check failed **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [March 29, 2021, 8:23pm UTC](https://community.graylog.org/t/https-signature-check-failed/19304 "2021-03-29T20:23:30Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![gsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gsmith/32/1222_2.png) [@gsmith](https://community.graylog.org/u/gsmith)\ **Post date:** [March 29, 2021, 11:17pm UTC](https://community.graylog.org/t/https-signature-check-failed/19304/2 "2021-03-29T23:17:30Z")
@tgabutti Hello, > [@tgabutti](#): > > PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed It could be several reasons why Graylog is complaining about your certificates. Couple that come to mind is the proper certificates being used? Can graylog access the keystore? Was the correct certificate inserted in the keystore? Is Graylog server.conf file configured correctly? As a troubleshooting tip have you tried not using Nginx for a reverse proxy and just run Graylog with HTTPS? Reason I ask this because someone else had a simulair issue, It ended up being his Nginx configuration causing problems. > [@Inputs not showing as running, but they seem to be anyway](https://community.graylog.org/t/inputs-not-showing-as-running-but-they-seem-to-be-anyway/19035/11): > > Alright, found the culprit. Accessing Graylog without passing through nginx indeed gives me a whole new user experience. A much better one, I may say. slight_smile The issue that sparked this topic, but also all the others I mentioned meanwhile are gone in direct access. Time to play around with my nginx config. Thank you so much for the suggestion, Greg. Much appreciated. As you can see there are many topics of HTTPS and TCP/TLS in the forum. [https://community.graylog.org/search?q=https](https://community.graylog.org/search?q=https) Hope this helps. --- _[View the full topic](https://community.graylog.org/t/https-signature-check-failed/19304)._