SSL Server Hangs After a While

[elvisyjlin]

Hi,
I'm building an API server with Django 2.2.1 and django-sslserver 0.20. The server worked normally at the beginning. But it hung after a couple of minutes. None of any kinds of requests (browser request, Postman request, python request, nodejs request, etc.) could get any response from the server. Moreover, the server did not print out any new coming requests.

It was just hanging there. Is it a bug or a kind of compatibility issues?

[belokopytov]

Have the same issue

[gwsampso]

+1

[nomadjourney]

Seeing the same issue with Django 2.2.2

[rob-deutsch]

I am getting a similar problem. I am trying to access the SSL server from two different browsers (Safari and Chrome) and it seems that connections to one browser locks out the other.

What I mean is that if I'm browsing a site in Safari then Chrome will be unable to access it. After a few minutes Chrome can access it, but then Safari won't be able to access it.

Neither browser errors straight away, which suggests that its making the TCP connection, but the server isn't doing anything with that TCP connection.

[ericjohney]

same here on django 2.1.10

[justinmayer]

I also just ran into this problem, which, if I'm not mistaken, has already been fixed and merged to master: #85

If so, the problem is that the fix is not present in a shipped release.

@battlemidget: Given that the last release was over two years ago, do you think you could find the time to increment the version number and release a new package to PyPI?

As a side note, this tendency for package releases to lag behind master is one that I have personally encountered dozens of times... including when the fault is entirely my own, in projects that I maintain! It's a shame because it means there are features and bug fixes in master that nearly nobody is benefiting from, and all because publishing new releases to PyPI is just cumbersome enough to prevent maintainers from prioritizing it. (And once again, I'm including myself in that group!)

I recently solved this problem by creating AutoPub, an open-source package that helps automate package releases on PR merge, which I just announced during my EuroPython talk last month in Basel, Switzerland. Benefits include:

• With almost no human input, every code contribution results in a new release in a matter of minutes.
• Every feature and bug-fix has its own release, without anyone having to remember to package and publish a new version.
• If a bug is found, it’s much easier to trace it to a specific release version.

Perhaps the best part is that all contributors get to issue their own releases. What better way to welcome new contributors than to reward them with a dedicated release composed entirely of their own work?

Since the announcement last month, I've added AutoPub to the projects I maintain:

• Pelican — PR adding AutoPub
• django-elevate — PR adding AutoPub
• django-autoslug — PR adding AutoPub

... and, of course, AutoPub releases itself via AutoPub.

As a maintainer, I have been thrilled with the results. I would be happy to submit a PR that adds AutoPub to this repository, assuming that would be of interest. What do you think, @battlemidget ?

[Moon-developer]

Has there been any progress on this issue. I just came across it. I have to restart the server everytime two people try access it because one locks the other out and then it hangs. If anyone has a method they came up with as a quick patch even I am willing to implement it at this point.

[johnthagen]

If so, the problem is that the fix is not present in a shipped release.

@battlemidget: Given that the last release was over two years ago, do you think you could find the time to increment the version number and release a new package to PyPI?

0.21 has been released, so we could see if the issue is still persisting.

[rob-deutsch]

For what its worth, I'm not getting the issue with 0.21.

[RuiPedroLeal]

Hello, i'm running a small internal project on version 0.22 and still got this issue (hangs after some time, hours or minutes). Any ideias on how to mitigate this?

[DaemondShu]

If so, the problem is that the fix is not present in a shipped release.

@battlemidget: Given that the last release was over two years ago, do you think you could find the time to increment the version number and release a new package to PyPI?

0.21 has been released, so we could see if the issue is still persisting.

Any fix for python2.7 version?

[johnthagen]

Any fix for python2.7 version?

@DaemondShu Python 2.7 is end of life so ideally you should try to migrate to a supported version of Python (3.6+).

https://www.python.org/doc/sunset-python-2/