# Inputs not starting **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [February 28, 2019, 5:50pm UTC](https://community.graylog.org/t/inputs-not-starting/9188 "2019-02-28T17:50:42Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JoeG](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joeg/32/193_2.png) [@JoeG](https://community.graylog.org/u/JoeG)\ **Post date:** [February 28, 2019, 5:50pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/1 "2019-02-28T17:50:43Z")
So I can pull up the GUI using https and even show the valid certificate. I can create inputs but cannot start any inputs. I get the following error: 2019-02-28T12:37:43.528-05:00 WARN [ProxiedResource] Unable to call [https://10.20.30.40:9000/api/system/inputstates](https://10.20.30.40:9000/api/system/inputstates) on node \<535aff1b-6b40-4208-bea5-827a6f560497\> javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.20.30.40 not verified: certificate: sha256/RjIlKT792ohmSxPEr6P3Md60UwEqR8LA7OI39LEOVvc= DN: [CN=graylog.example.com](http://CN=graylog.example.com), OU=IT1, O=Mine, L=Any, ST=Confused, C=US subjectAltNames: [[graylog.example.com](http://graylog.example.com), [greylog.example.com](http://greylog.example.com)] How can I change the behaviour to use the hostname instead of the IP? I also have this log entry: 2019-02-28T12:40:05.340-05:00 WARN [AbstractTcpTransport] receiveBufferSize (SO\_RCVBUF) for input SyslogTCPInput{title=syslog\_tcp\_5141\_linux, type=org.graylog2.inputs.syslog.tcp.SyslogTCPInput, nodeId=null} (channel [id: 0xdd8633b3, L:/0:0:0:0:0:0:0:0:5141]) should be 1048576 but is 212992. When I look in the GUI, the Receive Buffer Size is set to: 1048576; is it defined else or am I looking in the wrong place? ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 1, 2019, 9:15am UTC](https://community.graylog.org/t/inputs-not-starting/9188/2 "2019-03-01T09:15:33Z")
> Hostname 10.20.30.40 not verified: > certificate: sha256/RjIlKT792ohmSxPEr6P3Md60UwEqR8LA7OI39LEOVvc= > DN: [CN=graylog.example.com](http://CN=graylog.example.com), OU=IT1, O=Mine, L=Any, ST=Confused, C=US > subjectAltNames: [[graylog.example.com](http://graylog.example.com), [greylog.example.com](http://greylog.example.com)] Your created certificate does not include the IP of your Graylog - but that IP is used in the Graylog configuration that is why the certificate can’t be used for communication using the IP. ---
**Author:** ![JoeG](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joeg/32/193_2.png) [@JoeG](https://community.graylog.org/u/JoeG)\ **Post date:** [March 1, 2019, 4:45pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/3 "2019-03-01T16:45:13Z")
Thanks, in previous graylog versions I didn’t need to have SANs for the IP address in my certificate. Is there somewhere I can override this within my config? ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 1, 2019, 7:24pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/4 "2019-03-01T19:24:13Z")
what are your http\_\* settings? ---
**Author:** ![JoeG](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joeg/32/193_2.png) [@JoeG](https://community.graylog.org/u/JoeG)\ **Post date:** [March 1, 2019, 7:43pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/5 "2019-03-01T19:43:54Z")
grep -v “http\_” /etc/graylog/server/server.conf | grep -v “#” http\_bind\_address = 10.20.30.40:9000 http\_enable\_tls = true http\_tls\_cert\_file = /etc/graylog/certs/graylog.crt http\_tls\_key\_file = /etc/graylog/certs/graylog.pem http\_tls\_key\_password = XXX I do have this behind an HAProxy server. I compared the graylog 3.0 documentation for running as such and also compared against my 2.x graylog environment. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 1, 2019, 8:27pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/6 "2019-03-01T20:27:29Z")
please re-read the first three settings and their meaning [https://docs.graylog.org/en/3.0/pages/configuration/server.conf.html#web-rest-api](https://docs.graylog.org/en/3.0/pages/configuration/server.conf.html#web-rest-api) ---
**Author:** ![JoeG](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joeg/32/193_2.png) [@JoeG](https://community.graylog.org/u/JoeG)\ **Post date:** [March 5, 2019, 10:27pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/7 "2019-03-05T22:27:18Z")
Thanks, I recut the certificate to include the individual nodes in the SubjectAltNames (SAN) in addition to the load balanced name and added the following to /etc/graylog/server/server.conf: http\_publish\_uri = [https://graloy-node1.example.com](https://graloy-node1.example.com) Now the services are starting. Thank you. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [March 19, 2019, 10:27pm UTC](https://community.graylog.org/t/inputs-not-starting/9188/8 "2019-03-19T22:27:23Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.