elastic / elastic/logstash

Filebeats SSL/Cert Validity issue

Open
#4,926 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

Hi,

So I created a self signed ssl which starts at 13.28:

```
[root@web-01-iom ~]# openssl x509 -startdate -noout -in /etc/pki/tls/certs/logstash-forwarder.crt
notBefore=Mar 30 13:28:11 2016 GMT
```

When trying to (re)start Filebeat i get the following error:

```
2016/03/30 13:47:55.988952 transport.go:125: ERR SSL client failed to connect with: x509: certificate has expired or is not yet valid
Stopping filebeat: [ OK ]
Starting filebeat: 2016/03/30 13:47:56.110564 transport.go:125: ERR SSL client failed to connect with: x509: certificate has expired or is not yet valid
[ OK ]
```

Notice the date/time stamp? it's an hour behind, but the SSL cert is still valid..

The dateime on the server is actually:

```
[root@web-01-iom ~]# date
Wed Mar 30 14:48:24 BST 2016
```

EDIT:

Just to prove it hasn't expired..

```
[root@web-01-iom ~]# openssl x509 -enddate -noout -in /etc/pki/tls/certs/logstash-forwarder.crt
notAfter=Mar 28 13:28:11 2026 GMT

```

Let me know if you need anything else.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.