Any of you #python web client guru types out there, I got this weird problem.

I have some code that makes a request to a flask server (API); it generates a POST containing a apikey (password) and a mac address. You can think of these a user/password credentials set.

Before you start yelling at me about security, this login is used only to obtain a token of the usual sort, after which time all POST operations to the API are accompanied by the token.

The only thing is, it never gets that far.

No message ever appears on the flask server console concerning the request; and I get a 111 Connection Refused message on the client console. I also get a reason: "Too many connection attempts for this URL".

Thing is, this is code that has run in production unchanged for a couple of years. The salient change: A full debian upgrade.

Now mind you, this code runs in a python environment, with a very specific python version (3.7.3) and a very specific set of dependencies.

Anybody got any ideas?

This code runs on several machines. Only the upgraded ones are exhibiting this behavior.

TBF they are all running a copy of the same disk, and so all are running a copy of the error, so it's questionable whether the upgrade is the actual root cause.

@sparseMatrix maybe something has changed in the way front end does the post request? Browser update or Javascript dependency?

@wraptile

Thank you for the kind reply. During the few years in production, I have not worked with the code.

So imagine my surprise to discover that it was still pointed at a development server port.

I do not know how I ended up with such a copy of that file; I think it was customer-provided. It was supposed to be a copy of what was in production. In any case, no harm done.

All I had to do was stop knowing what was going on and follow the signs to what was ACTUALLY going on ;)

Cheers, and thanks again.

@sparseMatrix haha been there! Looking at the code when should have looked at the browser's devtools and saved hours.