# Quick feedback on Nginx Proxy Documentation **URL:** \ **Category:** Elastic Community and Ecosystem\ **Created:** [April 17, 2018, 5:53pm UTC](https://discuss.elastic.co/t/quick-feedback-on-nginx-proxy-documentation/128409 "2018-04-17T17:53:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Kerberos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kerberos/32/30093_2.png) [@Kerberos](https://discuss.elastic.co/u/Kerberos)\ **Post date:** [April 17, 2018, 5:53pm UTC](https://discuss.elastic.co/t/quick-feedback-on-nginx-proxy-documentation/128409/1 "2018-04-17T17:53:41Z")
Just a quick piece of feedback for the documentation on the _Playing HTTP Tricks with Nginx_ page. > **[Tips to secure Elasticsearch clusters for free with encryption, users, and more](https://www.elastic.co/blog/tips-to-secure-elasticsearch-clusters-for-free-with-encryption-users-and-more)** > > Elasticsearch security is now free. This post revisits and updates best practices for securing your clusters, including transport layer security (TLS), native and file realm authentication, authorization features, cluster and node isolation, Kibana... In the Basic Authentication section, there is an erroneous 'n' placed within the password encryption example. I copy-pasted the line to modify for some testing and didn't realize for a while why I couldn't authenticate to my ES instance via the reverse proxy. tl;dr: > $ printf "john:$(openssl passwd -crypt s3cr3t)n" \> passwords Should be: > $ printf "john:$(openssl passwd -crypt s3cr3t)" \> passwords ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 5:20am UTC](https://discuss.elastic.co/t/quick-feedback-on-nginx-proxy-documentation/128409/2 "2022-11-04T05:20:26Z")