Hi,
as long as you don't add your self-signed certificate to the trusted
certificates of your web browsers as well, that "insecure" notification
will remain.
Please consult the documentation of your web browser for this.
Cheers,
Jochen
On Wednesday, 15 February 2017 17:04:02 UTC+1, CTuser
Hi Jochen,
I've written it as follows:
GRAYLOG_SERVER_JAVA_OPTS=" -Xms1g -Xmx1g -XX:NewRatio=1 -server
-XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled
-XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
-XX:-OmitStackTraceInFastThrow
Hi,
you can add JVM settings to the GRAYLOG_SERVER_JAVA_OPTS variable.
Cheers,
Jochen
On Wednesday, 15 February 2017 13:03:45 UTC+1, CTuser wrote:
>
> Hi Jochen,
>
> here is the output of the JVM settings (/etc/sysconfig/graylog-server):
>
Hi Jochen,
here is the output of the JVM settings (/etc/sysconfig/graylog-server):
# Path to the java executable.
JAVA=/usr/bin/java
# Default Java options for heap and garbage collection.
GRAYLOG_SERVER_JAVA_OPTS=" -Xms1g -Xmx1g
Hi,
please refer
to http://docs.graylog.org/en/2.2/pages/configuration/file_location.html
for the specific location of the file for the JVM settings.
Cheers,
Jochen
On Wednesday, 15 February 2017 11:15:01 UTC+1, CTuser wrote:
>
> Hi Jochen,
>
> I already followed the "Adding a self-signed
Hi Jochen,
I already followed the "Adding a self-signed certificate to the JVM trust
store" section.
I also verified that the self-signed certificate has been added
successfully to the key store.
I don't know how to cause the JVM to pick up the new trust store.
According to the guide it has to
Hi,
the necessary steps are described in the documentation at
http://docs.graylog.org/en/2.2/pages/configuration/https.html#adding-a-self-signed-certificate-to-the-jvm-trust-store
.
Cheers,
Jochen
On Wednesday, 15 February 2017 09:14:03 UTC+1, CTuser wrote:
>
> Hi,
>
> I created self-signed
