Hi Aldo,
please refer to the manuals of OpenSSL (or any other program you're using
to create or convert private keys and your certificates):
- https://www.openssl.org/docs/manmaster/apps/pkcs8.html
- https://www.openssl.org/docs/manmaster/apps/x509.html
- https://www.madboa.com/geek/ope
Ok Thanks.
And the right procedure is?
On Monday, May 9, 2016 at 2:44:20 PM UTC+2, Jochen Schalanda wrote:
>
> Hi Aldo,
>
> it looks like you've been storing a private key in
> /etc/pki/tls/certs/graylog.pem instead of an X.509 certificate.
>
> Additionally, you really shouldn't post your privat
Hi Aldo,
it looks like you've been storing a private key in
/etc/pki/tls/certs/graylog.pem instead of an X.509 certificate.
Additionally, you really shouldn't post your private keys on a public
mailing list.
Cheers,
Jochen
On Wednesday, 4 May 2016 19:29:42 UTC+2, Aldo Pellini wrote:
>
> Hi,
>
Hi,
I have created a certificate with these commands:
942 openssl pkcs8 -topk8 -inform PEM -outform PEM - in graylog.pem -out
private_gray.pem -nocrypt
944 openssl pkcs8 -topk8 -inform PEM -outform PEM -in graylog.pem -out
private_gray.pem -nocrypt
Then I have copied these into pki direct
Hi Aldo,
On Tuesday, 3 May 2016 21:45:50 UTC+2, Aldo Pellini wrote:
>
> I have tried to do this but graylog shuts down.
>
What exactly do you mean with this? What's the error message?
Cheers,
Jochen
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" g
Hi,
I have tried to do this but graylog shuts down.
There is an useful guide to follow for creating valid certs?
Aldo Pellini
On Monday, May 2, 2016 at 11:53:11 AM UTC+2, Jochen Schalanda wrote:
>
> Hi Aldo,
>
> you need to enable HTTPS for both, the Graylog REST API and the web
> interface. Ot
Hi Aldo,
you need to enable HTTPS for both, the Graylog REST API and the web
interface. Otherwise your browser will issue those mixed content warnings
and block access to the (unencrypted) Graylog REST API.
See http://docs.graylog.org/en/2.0/pages/configuring_webif.html for details.
Cheers,
Jo
Sorry I have found on documentation that these is value is good.
Another issue I could not start an upgraded Graylog2 in HTTPS.
There is something that I have lost?
If I try to enable https GUI give to me following error:
Server currently unavailable
We are experiencing problems connecting to
I'm following upgrading guide and I have entered following command to our
ES cluster:
curl -s -XGET 10.12.39.19:9200/_all/_mapping | jq -r "keys[]"
It returns empty.
Also if I do command without jq I have only empty brackets as output:
curl -s -XGET 10.12.39.19:9200/_all/_mapping/index_range
Hi,
the upgrade instructions will be added to the Graylog documentation
at http://docs.graylog.org/en/2.0/
Cheers,
Jochen
On Friday, 29 April 2016 17:11:51 UTC+2, 123Dev wrote:
>
> Thanks Jochen for quick response.
> I look forward to the manual upgrade documentation.
>
> Would you drop a note
Thanks Jochen for quick response.
I look forward to the manual upgrade documentation.
Would you drop a note here when that is ready or if there is any page I can
monitor, it would be great.
Thanks
On Friday, April 29, 2016 at 10:54:40 AM UTC-4, 123Dev wrote:
>
> Hi Jochen,
>
> Any advice on upg
Hi,
upgrading the OVAs and AMIs (which both are using the Graylog omnibus
package) is currently not supported.
We're currently working on some documentation for manually upgrading those
virtual machine images in an existing setup.
Cheers,
Jochen
On Friday, 29 April 2016 16:54:40 UTC+2, 123Dev
Hi Jochen,
Any advice on upgrading AWS image based 1.3 deployment to 2.0?
The cluster is made of two Graylog Servers, two datanode servers and one
web portal (ES running on Graylog Servers and Datanode Servers, MongoDB
running on GS Servers).
Should one be upgrading ES and MongoDB on each insta
Ok Thank you Jochen
>
>>
--
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https
Hi,
you basically "just" need to upgrade Elasticsearch to version 2.3.2 (latest
stable at the point of writing), restart your ES cluster, and then upgrade
your Graylog server nodes (the web interface has been merged into the
server component).
Make sure to read
https://github.com/Graylog2/gra
My system is centos 6
Le jeudi 28 avril 2016 11:35:50 UTC+2, kaiser a écrit :
>
> Hello,
>
> Is there a method to ugrade from 1.3.4 to 2.0 please?
>
> regards.
>
>
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group
16 matches
Mail list logo
