Skip to content

Commit 3343240

Browse files
committed
Describe how to enable TLS/SSL connection properly
Originally reported by LukasJerabek in fluentd#3584. It turns out that this configuration example is confusing, because, while it explicitly enables the hostname verification, it still uses an IP address for connection. Fix it. Signed-off-by: Fujimoto Seiji <fujimoto@ceptord.net>
1 parent abee4bc commit 3343240

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

output/forward.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -473,7 +473,7 @@ If you have set up [TLS/SSL encryption](../input/forward.md#how-to-enable-tls/ss
473473
@type forward
474474
transport tls
475475
<server>
476-
host 192.168.1.2
476+
host example.com
477477
port 24224
478478
</server>
479479
</match>
@@ -486,9 +486,10 @@ If you are using a self-singed certificate, copy the certificate file to the for
486486
@type forward
487487
transport tls
488488
tls_cert_path /path/to/fluentd.crt # Set the path to the certificate file.
489-
tls_verify_hostname true # Set false to ignore cert hostname.
490489
<server>
491-
host 192.168.1.2
490+
# Set the remote server name. This name should match the Common Name
491+
# field in the certificate.
492+
host example.com
492493
port 24224
493494
</server>
494495
</match>

0 commit comments

Comments
 (0)