Hi All I installed a graylog server 4 on ubuntu 18 with elasticsearch-oss and nginx. The server is configured with https and a self signed certificate. I’m having problem with the server inputs, I can create the input with the port 1514 but the service didn’t start, in the server.log file I have t…

I believe permissions on cert files themselves is the only thing suggested. I haven’t done this personally, just relaying a suggestion I have seen on the forums. FYI

do you mean change the owner to graylog ubuntu user?

I created a new input and didn’t start, here is the log error 2021-02-19T10:12:06.060-05:00 INFO [InputStateListener] Input [Syslog TCP/602fd545a4bcb73e26ebd797] is now STARTING 2021-02-19T10:12:06.129-05:00 INFO [InputStateListener] Input [Syslog TCP/602fd545a4bcb73e26ebd797] is now RUNNING 20…

I really wish there was a definitive guide on how to get TLS/SSL going. I am still struggling to get it up and running myself. Is 192.168.0.2 the IP of your Graylog Server? I’m assuming you have the cluster all on the same server. The “not verified” part made me think of “Adding a self-signed ce…

Yes I did it, the only step that I miss is the next, beacuse I didn’t found were to do it: In order for the JVM to pick up the new trust store, it has to be started with the JVM parameter -Djavax.net.ssl.trustStore=/path/to/cacerts.jks . If you’ve been using another password to encrypt the JVM trus…

I just added the line in the script /etc/init.d/graylog-server on line 47 DAEMON_ARGS="$GRAYLOG_SERVER_JAVA_OPTS DAEMON_LOG_OPTION -Dgraylog2.installation_source={GRAYLOG_INSTALLATION_SOURCE:=unknown} -Djavax.net.ssl.trustStore=/etc/graylog/server/cacerts.jks -Djavax.net.ssl.trustStoreType=jks -Dja…

@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 nee…

Do I understand that the steps you outlined enabled you to create a TLS input? Did you also enable SSL on the web interface? Thank you, Zach.

Yes, I will try creating new certificates

HI gsmith I tried but I’m having the same error: WARN [AbstractTcpTransport] receiveBufferSize (SO_RCVBUF) for input SyslogTCPInput{title=Bla, type=org.graylog2.inputs.syslog.tcp.SyslogTCPInput, nodeId=0f4d5681-400c-44b8-b890-5fcac066222f} (channel [id: 0x8cf27397, L:/0:0:0:0:0:0:0:0%0:51412]) sh…

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

Graylog Central (peer support)

pguillermet (Pablo Guillermet) February 24, 2021, 11:48am 20

Thanks, yes the common name it’s ok

Topic		Replies	Views
Unable to start inputs after implementing HTTPS on Graylog web interface Graylog Central (peer support)	5	2680	January 11, 2022
SSL Issues ProxiedResource Unable to call Hostname not verified Graylog Central (peer support)	4	2830	December 1, 2021
Inputs show failed, but ports are open and logs are coming in Graylog Central (peer support) basic-configuration	6	1125	April 14, 2022
Graylog2 Using https Graylog Central (peer support)	9	8219	November 15, 2017
Setting up HTTPS connection error - Unreadable or missing HTTP private key Graylog Central (peer support)	26	4531	May 11, 2022

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

Related topics