# Graylog2 https Error on Chrome **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [October 27, 2017, 3:39am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936 "2017-10-27T03:39:15Z")\ **Posts on this page:** 8\ **Page:** 1
**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:** [October 27, 2017, 3:39am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/1 "2017-10-27T03:39:16Z")
Hello All, Question about self-signed Certs for Graylog using HTTPS. I’m using CentOS 7 Virtual machine, all in one Graylog Server, My installed Certificates work from the instruction use from here: [https://github.com/3vi1john/graylog](https://github.com/3vi1john/graylog) Chrome states “Not Secure” on the URL I opened Developer Tools on Chrome and noticed the following; ![Graylog-cert-error](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/5/5edd61dcc07fb8ee0936c8dc3282a7f5dbf48a88.png) The errors “There are issues with the site’s certificate chain (net::ERR\_CERT\_COMMON\_NAME\_INVALID)” And “The certificate for this site does not contain a Subject Alternative Name extension containing a domain name or IP address” Tried to fix this issue by creating a file named openssl-graylog.cnf and using it when making my certificates. Instruction used; [http://docs.graylog.org/en/2.3/pages/configuration/https.html](http://docs.graylog.org/en/2.3/pages/configuration/https.html) , No joy I also tried to modify my /etc/pki/tls/openssl.cnf file as shown below; [v3\_ca] subjectAltName= @alt\_names [alt\_names] DNS.1 = FQDN IP.1 = IPaddress I did some research and found most, if not all browsers do not like Self-Signed Certificates and to remove these errors properly I need SSL certificate provider (certificate authority). Chrome Secure resources does state “All resources on this page are served securely.” I was wondering if there is something else I could do to fix Certificate error & Subject Alternative Name error. ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [October 27, 2017, 7:16am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/2 "2017-10-27T07:16:40Z")
> [@gsmith](#): > > I was wondering if there is something else I could do to fix Certificate error & Subject Alternative Name error. No, you have to import your self-signed certificate(s) or the CA you’ve signed them with into the certificate store of your browser. See [https://support.securly.com/hc/en-us/articles/206081828-How-to-manually-install-the-Securly-SSL-certificate-in-Chrome](https://support.securly.com/hc/en-us/articles/206081828-How-to-manually-install-the-Securly-SSL-certificate-in-Chrome) for an example. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [October 27, 2017, 8:40am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/3 "2017-10-27T08:40:20Z")
you might want to use the following script that helps you with creating the self signed certificates: > and gives you the ability to easily adopt the needed command to your own needs. regards Jan ---
**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:** [October 27, 2017, 9:59pm UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/4 "2017-10-27T21:59:39Z")
@ jochen Thank for your response, I did try to insert a certificate into Chrome, I still received the same error. I was not sure which certificate I should insert so, I download it from Chrome \> Developer Tools \> View certificate. This opens Certificate window \> then clicked on tab called “Details” selected “all” , Click "Copy to File"then executed [https://support.securly.com/hc/en-us/articles/206081828-How-to-manually-install-the-Securly-SSL-certificate-in-Chrome](https://support.securly.com/hc/en-us/articles/206081828-How-to-manually-install-the-Securly-SSL-certificate-in-Chrome). Still errors out. ---
**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:** [October 28, 2017, 1:25am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/5 "2017-10-28T01:25:50Z")
@jan Thank for the tip on the Script, Unfortunately I’m still running into the same issue, Here is a couple of screen shots. This was executing script “create\_ssl\_sertc.sh” ![graylog-ssl-cert](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/d/d20461ed23f0d5796b348eec5edaeaf6852001ad.png) The results were the same as shown below, ![SSL-error-report](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/3/3deb1ee75973f40484cc620e62335c84c416c72c.png) Not sure what I’m doing wrong. Any advice would be appreciated. NOTE: Also tried with adding Cert to Chrome ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [October 28, 2017, 8:49am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/6 "2017-10-28T08:49:47Z")
@gsmith its simple your hostname (you use in chrome) is `test-graylog.enseva-labs.net` and your certificate is only created for `test-graylog`. correct that and it should work ---
**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:** [November 1, 2017, 4:54am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/7 "2017-11-01T04:54:37Z")
@jan Fixed: 🙂 Thanks again jan ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [November 15, 2017, 4:54am UTC](https://community.graylog.org/t/graylog2-https-error-on-chrome/2936/8 "2017-11-15T04:54:49Z")
Closed on November 15, 2017, 4:54am UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.