Unable to start inputs after implementing HTTPS on Graylog web interface

[gsmith]

Hello,
I have had this issue before which I was able to log into the web interface but my Inputs were not working.

My check list consist of the following.

• Make sure I’m actually using the correct certificates.
• Check Keystore for the correct certificates were installed.
• Make sure I created the proper keystore.
• Permission on the Certificates must be owned by Graylog, if not Graylog will be unable to find certification path.

@foss4ever

WARN [ProxiedResource] Unable to call https://graylog.[domain redacted].com:9000/api/system/inputstates/61d5ab8834b9fa6fd275c639 on node <265afac6-d5af-47ae-b107-7f61973c5a05>: PKIX path building failed:sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

So the moral of the story is…

@foss4ever

unable to find valid certification path to requested target

This could be an error on your certificate/s created, OR your using a incorrect one for your input.

Here are a couple post you may want to look at, This helped for understanding what I need to do.

Graylog3 with https (easy tutorial)

My ambient test: -Oracle Linux 7.6 (VMware 15); -Network: NAT; -Graylog3, MongoDB and Elastic: running together; Documentation base for RPM distro. First of all, read Docs » Configuring Graylog » Using HTTPS 0- mkdir /etc/ssl/certs/graylog/ && cd /etc/ssl/certs/graylog/ 1- openssl req -x509 -days 1095 -nodes -newkey rsa:2048 -config openssl-graylog.cnf -keyout pkcs5-plain.pem -out cert.pem 2- openssl pkcs8 -in pkcs5-plain.pem -topk8 -nocrypt -out pkcs8-plain.pem 3- openssl pkcs8 -in pk…

WARN [ProxiedResource] Unable to call and unable to start inputs

@pguillermet I’m sorry to hear you still having problems. This did take some time for me to understand how certificates work with graylog-server. One thing was clear, the certs need to be in the right format. Graylog needs to be able to access certs for the input (i.e. permissions). Graylog needs to be able to access the keystore. I can show you what i did but I also know everyone environment is a little bit different, so you might need configure these steps for your needs. The following s…

Hope that helps