Yes, i'm working in a company. But in that case I make a selfed signed
certificate (i followed this part of the graylog doc :
http://docs.graylog.org/en/2.0/pages/configuring_webif.html#https-setup and
i see no CA usage ^^)

2016-06-06 13:35 GMT+02:00 kaiser <[email protected]>:

> Are you working in a company?
>
> In that case you should ask for your enterprise certificate (with the
> passphrase for graylog)  and do the following
>
>
> http://mikepilat.com/2011/05/adding-a-certificate-authority-to-the-java-runtime.html
>
>
> Le lundi 9 mai 2016 11:24:09 UTC+2, Earest a écrit :
>
>> Hello,
>>
>> After some hours trying to configure tls encripting without success, i
>> come here to ask for some help.
>>
>> *Server configuration :*
>>
>> Derbian 8
>> Graylog 2.0.0
>> Mongodb 2.4.10
>> Java 8u92+8u91
>> Elasticsearch 2.3.2
>>
>>
>> *Graylog tls options *:
>>
>> rest_enable_tls = true
>>> rest_tls_cert_file = /etc/ssl/temp/graylog.pem
>>> rest_tls_key_file = /etc/ssl/temp/key_pk8.pem
>>> rest_tls_key_password =
>>> web_enable_tls = true
>>> web_tls_cert_file = /etc/ssl/temp/graylog.pem
>>> web_tls_key_file = /etc/ssl/temp/key_pk8.pem
>>> web_tls_key_password =
>>
>>
>>
>> *Now my tls configuration step by step :*
>>
>>
>> #cert and key creation (-x509 and pkcs10)
>>
>>> sudo openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout
>>> key.pem -out graylog.pem
>>
>>
>> #converting to pkcs8 as indicated in the conf file
>>
>>> sudo openssl pkcs8 -nocrypt -topk8 -in key.pem -out key_pk8.pem
>>>
>>
>> #adding cert to keystore
>>
>>> sudo $JAVA_HOME/bin/keytool -import -alias gray_key -file
>>> /etc/ssl/temp/graylog.pem -keystore /etc/ssl/graylog.jks
>>>
>>
>> #adding keystore to java truststore with the following shell script :
>>>
>>> #!/bin/bash
>>> export JAVA_OPTIONS="-Djavax.net.ssl.trustStore=/etc/ssl/graylog.jks
>>> -Djavax.net.ssl.trustStorePassword=mypassword"
>>
>>
>> After that i restart my graylog server and get some warn in my log
>> (looping without interruption):
>>
>> 2016-05-09T11:09:48.176+02:00 WARN  [ProxiedResource] Unable to call
>>> https://serverIp:12900/system/metrics/multiple on node
>>> <cf9d4d3b-bfce-4cde-a2e6-db0a7c247ad4>, caught exception:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target (class
>>> javax.net.ssl.SSLHandshakeException)
>>> 2016-05-09T11:09:48.178+02:00 WARN  [ProxiedResource] Unable to call
>>> https://serverIp:12900/system/inputstates on node
>>> <cf9d4d3b-bfce-4cde-a2e6-db0a7c247ad4>, caught exception:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target (class
>>> javax.net.ssl.SSLHandshakeException)
>>
>>
>> If i connect to the the web page of graylog all my input are stop and  I
>> can't start them:
>>
>> I got the following error on the web page (pop-up message):
>>
>>> Input 'Input_name' could not be started
>>> Request to start input 'Input_name' failed. Check your Graylog logs for
>>> more information.
>>
>>
>> And here the associated log :
>>
>>> 2016-05-09T11:15:28.122+02:00 WARN  [ProxiedResource] Unable to call
>>> https://serverIp:12900/system/inputstates/5727554fe4b0c113c6180c6e on
>>> node <cf9d4d3b-bfce-4cde-a2e6-db0a7c247ad4>, caught exception:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target (class
>>> javax.net.ssl.SSLHandshakeException)
>>
>>
>> PS: After adding an exception for login page : https://serverIp:9000/ i
>> need to add one for https://serverIp:12900/system/cluster/node or i get
>> this error :
>>
>> We are experiencing problems connecting to the Graylog server running on 
>> *https://serverIp:12900//
>>> <https://serverIp:12900//>*. Please verify that the server is healthy
>>> and working correctly.
>>>
>>> You will be automatically redirected to the previous page once we can
>>> connect to the server.
>>>
>>> Do you need a hand? We can help you
>>> <https://www.graylog.org/community-support>.
>>>
>>> ------------------------------
>>>
>>>> This is the last response we received from the server:
>>>> Error message
>>>> Bad request
>>>> Original Request
>>>> GET https://serverIp:12900/system/cluster/node
>>>> Status code
>>>> undefined
>>>> Full error message
>>>> Error: Request has been terminated Possible causes: the network is
>>>> offline, Origin is not allowed by Access-Control-Allow-Origin, the page is
>>>> being unloaded, etc.
>>>> Possible causes: the network is offline, Origin is not allowed by
>>>> Access-Control-Allow-Origin, the page is being unloaded, etc.
>>>
>>>
>> If you have any question to ask, I stay at your disposal.
>>
>> Earest
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Graylog Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/graylog2/uiv3tsrckEU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/graylog2/8941b59e-80da-446a-a78d-0be3412ad080%40googlegroups.com
> <https://groups.google.com/d/msgid/graylog2/8941b59e-80da-446a-a78d-0be3412ad080%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/CAPU%3DbGgojFex9sKow45fQbP7EvXvSZPd_33HKBL99WZYip%3D3yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to