Closed DeLoWaN closed 5 years ago
Fix pushed to develop branch. Should be merged to master shortly.
@pcasa @royrusso I just ran into this issue and was wondering why elasticsearch-HQ would try to connect to port 53. Any chance this fix can be merged into develop please?
Is this not merged in to develop yet? Seems that @pcasa did.
Ah ok. I'm using the latest docker image and it's not in there unfortunately.
There should be a docker image for the develop branch.
Fixed half a year ago but still not fixed in the latest docker image?
Should be on the develop docker image. I will hopefully do a release this week. :-)
Should be in master. If still broken, please reopen this or create a new ticket.
Thank you! I can confirm this to be fixed.
General information
Issue Description
When I connect with a username/password, if the password starts with a digit, ElasticHQ considers it as the port of the elasticsearch cluster. See in the console of the browser.
Source Code / Logs
For example, the URL:
https://test:1test@localhost:9200
ElasticHQ tries to connect to:
As you can see, the port is wrong.