Hi,
there isn't any known issue, but I have a question about your configuration.
Which kind of client you are expecting to connect on "/poll/" location?
The default behavior is to use chunked encoding responses on locations with "push_stream_subscriber" derective without any argument.
If you are planning to use only polling or long polling clients on these location set the proper configuration.
What I mean is, if you connect on this location the default behavior is create a stream to send messages that "never" closes.
If you end the connection on client side, after receive a message as example, it will remain open on server side, until the server detects that the client has gone.
While using https this detection take a longer time to happens and you may have a problem of reaching the number of configured connections on each worker. Resulting on the problem of nginx does not accept any new connection.
Check the nginx error log to see if there is any problem.
Regards,
Wandenberg