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
Error after binding to socket and port in one config #1986
Comments
This is a bug. But, I believe if you list the unix bindings last, it should work. I wrote tests for both 'orderings', and I'll submit a PR... |
@MSP-Greg Yes, all works fine after changing bind position. Thank you for quick answer |
Thanks for testing quickly. Next release should fix the issue (no work-around needed). |
Closed
MSP-Greg
added a commit
to MSP-Greg/puma
that referenced
this issue
Sep 29, 2019
1. Fix mult binds when unix is first, followed by ip bind. See issue puma#1986. 2. When localhost is used for ssl or tcp, output actual ip's bound to. 3. Fix issues with IPv6 bind logging (brackets). 4. Move ssl context initialization code from Binder#parse to new method, #ssl_ctx_init.
nateberkopec
added a commit
that referenced
this issue
Oct 1, 2019
This was referenced Mar 9, 2021
Merged
This was referenced Mar 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Puma can not to be configuring for work with socket and port in one time.
In previous version (4.1.1) all work fine.
Error:
Puma config:
To Reproduce
File with application (app.rb):
File with puma config (config.puma.rb)
sinatra config (config.ru):
Gemfile:
Dockerfile:
I created a small project to reproduce this issue. It is attached to the issue.
I think this method has error.
@ios
class instance is a array with TCPServer and UNIXServer objects(addind TCPServer, addind UNIXServer), but this array is being processed only in tcp section (this).
project.zip
The text was updated successfully, but these errors were encountered: