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

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
2021-02-19T10:12:06.137-05:00 WARN [AbstractTcpTransport] receiveBufferSize (SO_RCVBUF) for input SyslogTCPInput{title=InputTCP, type=org.graylog2.inputs.syslog.tcp.SyslogTCPInput, nodeId=0f4d5681-400c-44b8-b890-5fcac066222f} (channel [id: 0xdd930caf, L:/0:0:0:0:0:0:0:0%0:1514]) should be 1048576 but is 425984.
2021-02-19T10:12:07.075-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:07.282-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:07.285-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates/602fd545a4bcb73e26ebd797 on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:07.547-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:08.474-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:09.139-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:10.471-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:11.139-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:13.206-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:13.207-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

2021-02-19T10:12:14.050-05:00 INFO [InputStateListener] Input [Syslog TCP/602fd545a4bcb73e26ebd797] is now STOPPING
2021-02-19T10:12:14.056-05:00 INFO [InputStateListener] Input [Syslog TCP/602fd545a4bcb73e26ebd797] is now STOPPED
2021-02-19T10:12:14.057-05:00 INFO [InputStateListener] Input [Syslog TCP/602fd545a4bcb73e26ebd797] is now TERMINATED
2021-02-19T10:12:14.821-05:00 WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:

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 certificate to the JVM trust store” from here:

https://docs.graylog.org/en/4.0/pages/configuration/https.html

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 trust store than the default changeit , you additionally have to set the JVM parameter -Djavax.net.ssl.trustStorePassword=secret .

Most start and init scripts for Graylog provide a JAVA_OPTS variable which can be used to pass the javax.net.ssl.trustStore and (optionally) javax.net.ssl.trustStorePassword system properties.

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 -Djava.library.path=/usr/share/graylog-server/lib/sigar -jar $JAR_FILE server -p $PIDFILE -f /etc/graylog/server/server.conf $GRAYLOG_SERVER_ARGS"

But still having the message “WARN [ProxiedResource] Unable to call”

@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 needs to be able to access the keystore. I can show you what i did but I also know everyone environment is a little bit different, so you might need configure these steps for your needs. The following steps is for CentOS 7 which has Elasticsearch, MongDb, and Graylog all on one Virtual machine. This helped me understand how and what to configure before I went into production envirment. An older problem I had with this was my DNS entry for my server. I had to make sure the Reverse lookup was configured.

  1. Navigate to the following directory as follow;
    NOTE: I looked for my JAVA keystore called CACERTS.
  • cd /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/security
  1. change the default password for Java CAcert store. Default password is changeit
  • keytool -storepasswd -keystore /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/security/cacerts

  • Type “changeit”

  • New-PASS Type “secret” /// this will be configured in graylog configuration file

  1. Generate Certs for Graylog.
  • keytool -genkey -alias dns.name.of.server -keyalg RSA -validity 365 -keystore keystore.jks
  • openssl req -x509 -days 365 -nodes -newkey rsa:2048 -keyout pkcs5-plain.pem -out cert.pem
  • openssl pkcs8 -in pkcs5-plain.pem -topk8 -nocrypt -out pkcs8-plain.pem
  • openssl pkcs8 -in pkcs5-plain.pem -topk8 -v2 des3 -out pkcs8-encrypted.pem -passout pass: secret
  • keytool -list -v -keystore keystore.jks -alias dns.name.of.server
  • keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12 -deststoretype PKCS12
  • openssl pkcs12 -in keystore.p12 -nokeys -out graylog-certificate.pem
  • openssl pkcs12 -in keystore.p12 -nocerts -out graylog-pkcs5.pem
  • openssl pkcs8 -in graylog-pkcs5.pem -topk8 -out graylog-key.pem
  1. Openjdk use this line. The password it requests is the password you changed in step 2.
  • keytool -import -trustcacerts -file graylog-certificate.pem -alias dns.name.of.server -keystore /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4.x86_64/jre/lib/security/cacerts
  1. Move certificates to graylog folder
  • NOTE: When I first started I found out by moving the files to Graylog Directory was easy for me to get the Inputs started and HTTPS enable for Graylog. Since Graylog owns this directory it was made simple. I have grown from this into something better but I found it to be a good learning experience to start with.
  • move all *.pem, *.p12 and *.jks files to /etc/graylog/
    and chown graylog:graylog -R /etc/graylog
    so that the graylog user has access to them
  1. Edit /etc/graylog/server/server.conf
  • http_enable_tls = true
  • http_tls_cert_file = /etc/ssl/certs/graylog/graylog-certificate.pem
  • http_tls_key_file = /etc/ssl/certs/graylog/graylog-key.pem
  • http_tls_key_password = secret
  1. Restart graylog and tail -f server.log
  • systemctl restart graylog-server
  • tail -f /var/log/graylog/server/server.log

My input configuration.

I hope this helps.

The following link/s help me understand how to make this happen.

https://docs.graylog.org/en/4.0/pages/configuration/https.html

1 Like

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]) should be 1048576 but is 425984.
INFO [InputStateListener] Input [Syslog TCP/6034053c8ec95d280ba22fb5] is now RUNNING
WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/metrics/multiple on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:
certificate: sha256/fj02ozJJViJ2Qz7Zjeel+FmYfyLvI9ljY3w2R6OvJAk=
WARN [ProxiedResource] Unable to call https://192.168.0.2:9000/api/system/inputstates/6034053c8ec95d280ba22fb5 on node <0f4d5681-400c-44b8-b890-5fcac066222f>: Hostname 192.168.0.2 not verified:
certificate: sha256/fj02ozJJViJ2Qz7Zjeel+FmYfyLvI9ljY3w2R6OvJAk=

Thanks

Yes and yes.
You can see the input I use from above.


The certs graylog-certificate.pem and graylog-key.pem I used for my Input, and graylog-certificate.pem is also used for HTTPS, I have changed things around since then, but for learning this was my first step.

I do have notes stating when I created my certs to use the Fully Quailified Domain Name (FDQN), Make sure my host name matched my certifcates, also my alias was the same name as my FDQN when I inserted my certificates into the keystore.

@pguillermet

Can you share your Server configuration file?
Since your using IP Address I take it you dont have a domain Controller in your environment?
Have you tried configuring your /etc/hosts file? Just a thought.

Here is one of my post while back, hope this will be able to help you figure out your problem.
My first step was just getting HTTPS enabled , then I moved to a INPUT using TCP/SSL.
Seams like your machine cant find your cert with IP Address (192.168.0.2). Question when you executed the steps I showed you from above, did you reconfigure this?

@pguillermet @dickinsonzach
Have you seen this.

Hi, where I have to set the COMMON NAME?

@pguillermet
Example:

[root@graylog bin]# openssl req -x509 -days 365 -nodes -newkey rsa:2048 -keyout pkcs5-plain.pem -out cert.pem
Generating a 2048 bit RSA private key

writing new private key to ‘pkcs5-plain.pem’

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter ‘.’, the field will be left blank.

Country Name (2 letter code) [XX]:us
State or Province Name (full name) :NewYork
Locality Name (eg, city) [Default City]:newyork
Organization Name (eg, company) [Default Company Ltd]:comp
Organizational Unit Name (eg, section) :admin
Common Name (eg, your name or your server’s hostname) []:server.domain.com

Thanks, yes the common name it’s ok

@gsmith , thank you so much! These instructions got me up and running with SSL on the web interface. it will take me a bit longer to test a TLS input, but wanted to thank you for this. Thank you, Zach.

1 Like

If it helps, I have what I used to test here:

1 Like

Which I now recall that you were already on that thread :upside_down_face: . In any case, happy to help if you run into issues.

@dickinsonzach
Your more then welcome. I also had a hard time, mainly because I was fairly new and creating Self-Singed Certificates and working with Graylog. Glad I was able to help.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.