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

Influxdb can be reachable via any port #607

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

b3n4kh
Copy link
Contributor

@b3n4kh b3n4kh commented Mar 16, 2020

I see no reasen why Influxdb should only allow highports. For example my setup where I have my Influxdb reachable via a reversproxy on port 443.

@lbetz
Copy link
Contributor

lbetz commented Mar 16, 2020

Ok, but why you didn't send it yesterday? I created a new bugfix release a few minutes ago.

@b3n4kh
Copy link
Contributor Author

b3n4kh commented Mar 16, 2020

Sorry didn't notice, I actually just wrote the fix today. Should I reopen the PR again at another point in the future, or can it stay open?

@lbetz
Copy link
Contributor

lbetz commented Mar 16, 2020

Not your fault. I'd like to do some mimimimi.
Of course it can be stood open. I will merge the PR in the near future and build a new bug fix release 2.3.4, maybe at the end of thie week.

@lbetz lbetz added this to the 2.4.0 milestone Mar 24, 2020
@lbetz lbetz merged commit 225478f into voxpupuli:master Mar 24, 2020
@b3n4kh b3n4kh deleted the influx-port-fix branch March 25, 2020 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants