Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs: tell customers about likely CORS issues #37

Open
Alex-At-Home opened this issue Apr 12, 2019 · 1 comment
Open

Improve docs: tell customers about likely CORS issues #37

Alex-At-Home opened this issue Apr 12, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@Alex-At-Home
Copy link
Owner

errors like:

ERROR [10:[email protected]]: status = [unknown], msg = [No Living connections], query = [/_cat/indices?format=json]

probably mean one of two things - either you're pointing at the Kibana, or the cluster does not have CORS setup (which seems to be necessary from 7.0 up)

@Alex-At-Home Alex-At-Home added the enhancement New feature or request label Apr 12, 2019
@Alex-At-Home
Copy link
Owner Author

Note I believe that the following CORS settings are desired for max security:

http.cors.enabled: true
http.cors.allow-origin: "https://n-zps6avz5zp6tamkkazpk2btgl7vaa4bckyf5ngi-*-script.googleusercontent.com"
http.cors.max-age: 86400
http.cors.allow-methods: GET
http.cors.allow-headers: "Authorization, Access-Control-Allow-Headers, Origin, Accept, X-Requested-With, Content-Type, Content-Length, Access-Control-Request-Method, Access-Control-Request-Headers"
http.cors.allow-credentials: true

(Testeed with a different user, and we had the same first bit but i had 0hl vs his 3hl in the middle?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant