locness-cors.duckdns.org is down and here's why

So I have been running this cors-anywhere instance on my home network for 1 or 2 years (along with my website and stuff), and I used it in a few projects like CNRTLReader.

It never occured to me that it could be used to access HTTP stuff within my home network, until I found an article explaining this kind of issues by chance.
That is obviously something I did not intend to allow.

Sadly there currently seems to be no way to blacklist access to some hosts in cors-anywhere. There seems to have been attempts to integrate this functionality, but nothing seems currently available. [1]

Until I look further into this, I have chosen to shut locness-cors.duckdns.org down. I will try to find a way to make my things which rely on it work again, however I cannot say that I will keep on hosting a cors-anywhere service.

If anyone relied on this service, I am very sorry for the inconvenience caused. I urge you to find an alternative, and to tell me about it.

The possibilites I have to investigate are to patch cors-anywhere, host it within a dedicated network, or find another usable public instance ( cors-anywhere.herokuapp.com is now very limited).

[1] Relevant issue/PR threads :