-
Notifications
You must be signed in to change notification settings - Fork 163
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
[BUG] - Cannot connect to cluster with special characters in password #10
Comments
Hi, thank you for reporting this bug. Sadly i cannot reproduce the issue, even with the exact same config that you provided. Do you see any error messages in the browser console (press F12, then select the "console" tab) when you try to connect to your cluster? |
Hm, thx for the update. To you have any special characters in your password? That might be the issue, i will check that. |
Seems that special characters don't work, thanks again for noting this. I already fixed it on develop and will release a new version in the following days. You can always build elasticvue yourself manually or via docker to use the latest version. |
Yes, my password contains '#', so I've tried to use '%23' instead but the same error. |
Hey @asdfII , just letting you know that i published a new version (0.16.1) that will hopefully fix the issue. You can update the firefox addon manually or wait for it to update automatically, either way you should be able to connect to your cluster. You also do not need to escape the password, you can enter is as-is. |
Description
Like this: http://10.112.17.82:9201/
Like this: http://elastic:[email protected]:9201/
NOTICE: But It works with chrome extension Elasticsearch Head!
Steps To Reproduce
Anytime
Screenshots
Environment
OS: Ubuntu 16.04
Browser: Firefox 70.0.1
Elaticsearch: 6.8.4 (x-pack on)
Elasticvue: 0.16.0
Running Mode: firefox add-ons
Important Elasticsearch Settings:
http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: X-Requested-With,Content-Type,Content-Length,Authorization
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: certs/elastic-certificates.p12
The text was updated successfully, but these errors were encountered: