HTTP 451 error “Service unavailable from a restricted location…”

This article is about the Binance Websocket API, if you want to redirect a REST connection to Binance via a SOCKS5 proxy, please read this article.

A SOCKS5 server is a type of proxy server that routes network traffic between a client and a server. It allows clients to bypass internet restrictions and access restricted content by using a different IP address.

I will explain in this article how to create a SOCKS5 proxy server using Linux and how to configure the websocket connection in Python to access the Binance API through the SOCKS5 proxy.

For this solution you need a simple virtual cloud Linux server such as a 4.51 EUR server with 20TB traffic volume included from HETZNER CLOUD, which supports the required traffic volume for the SOCKS5 proxy, and you need a working Python 3.8+ environment for the Python script!

We would like to explicitly point out that in our opinion US citizens are exclusively authorized to trade on Binance.US and that this restriction must not be circumvented!

The purpose of supporting a SOCKS5 proxy in the UNICORN Binance Suite and its modules is to allow non-US citizens to use US services. For example, Github actions with UBS will not work without a SOCKS5 proxy, as they will inevitably run on servers in the US and be blocked by Binance.com. Moreover, it also seems justified that traders, data scientists and companies from the US analyze binance.com market data — as long as they do not trade there.

1. Step — Set up the SOCKS5 service

There are countless ways to create a SOCKS5 proxy:

• danted SOCKS server

• tinyproxy

• openssh

• and many more …

The following instructions are for Debian and Ubuntu — for CentOS, RedHat, AWS EC2 and other Linux distributions that use `yum` as a package manager please follow these instructions.

danted SOCKS server

Project homepage: https://www.inet.no/dante/

• Log into your Linux server where you want to install the SOCKS5 proxy and get root privileges:
  sudo -i

• Install with apt:
  apt update
apt install dante-server

Info: After the installation dante does not work and still throws errors because it has not been configured yet!

• Test the installation with:
  danted -v
  Info: In Ubuntu and other distributions the danted can also be called sockd.

• Now edit the configfile of danted with nano or vi:
  nano /etc/danted.conf
  or
  vi /etc/danted.conf
  and set the following configuration, replace the IP “1.2.3.4” with your client IP of the Python script or use “0.0.0.0/0" as wildcard (please consider your security concept!):

logoutput: stderr  
logoutput: /var/log/danted.log  
internal: eth0 port = 1080  
external: eth0  
socksmethod: username none #rfc931  
client pass {  
        from: 1.2.3.4/32 to: 0.0.0.0/0  
        log: connect disconnect error  
}  
socks pass {  
        from: 1.2.3.4/32 to: 0.0.0.0/0  
        log: connect disconnect error  
}

• Start danted:
  $ systemctl start danted

• Check the status:
  systemctl status danted

• If desired create an autostart for danted:
  systemctl enable danted

If you have chosen a server from HETZNER CLOUD, here is a detailed step by step Dante SOCKS5 Proxy installation guide tailored to Hetzner servers.

2. Step — Test the SOCKS5 Proxy

Before you start testing, open a stream of the logfile on your server console, so you can watch all of Dante’s actions:
tail -f /var/log/danted.log

There are many ways to test the new SOCKS5 proxy:

Firefox:
“Settings” -> search for “proxy” -> enter the SOCKS5 proxy address and port number. Open https://ipchicken.com and check the IP address.

Putty:
Open Putty and click on “Connection” -> “Proxy” -> enter the SOCKS5 proxy address and port number. Open a SSH connection.

curl:
This should return your public IP address:
curl -x socks5://<your_ip_server>:<your_danted_port> ifconfig.co

Or with the python script we create next.

3. Step — The Python script

For the websocket connection to the Binance API we use the UNICORN Binance Websocket API. It directly allows the use of a SOCKS5 proxy and is configured via the parameters socks5_proxy_server, socks5_proxy_user, socks5_proxy_pass and socks5_proxy_ssl_verification.

Please note that the proxy support is only cleanly supported from unicorn-binance-websocket-api 2.0.0 and higher.

Install/upgrade the dependencies:
$ python3 -m pip install unicorn_binance_websocket_api
Info: https://pypi.org/project/unicorn-binance-websocket-api

Save or copy this script to your system and replace “1.2.3.4” in _socks5_proxy_ with the IP address of your Socks5 Proxy server.

Start the file:
python3 ubwa\_socks5\_proxy.py

You can find the full documentation for unicorn-binance-websocket-api here: https://oliver-zehentleitner.github.io/unicorn-binance-websocket-api

I hope you found this tutorial informative and enjoyable!

Thank you for reading, and happy coding!

Image source: https://pixabay.com

REST API is a simple and easy-to-use method that allows you to download historical data from Binance, but also to trigger functions such as creating a new order. You can use Unicorn Binance REST API, a sub module of the Unicorn Binance Suite, to make REST API calls and retrieve data in a JSON format.

WebSocket API, on the other hand, is a more advanced method that allows you to stream real-time data from Binance. You can use Unicorn Binance WebSocket API, another sub module of the Unicorn Binance Suite, to subscribe to WebSocket streams and retrieve data in a JSON format.

Unicorn Binance Suite is a comprehensive Python library for interacting with the Binance API. It consists of several sub modules, including Unicorn Binance REST API and Unicorn Binance WebSocket API, as well as other sub modules for trading, order management, and more.

To get started with Unicorn Binance Suite, you’ll need to install it using pip:

$ pip install unicorn-binance-suite

Or with conda:

$ conda install -c conda-forge unicorn-binance-suite

Once you have it installed, you can import the sub modules you need and start making API calls:

from unicorn\_binance\_rest_api.manager import BinanceRestApiManager  
  
ubra = BinanceRestApiManager(exchange='binance.com')  
  
klines = ubra.get_klines(symbol='BTCUSDT', interval='1h')  
print(klines) 

This example uses the UNICORN Binance REST API to download klines data for the BTCUSDT trading pair with a 1-hour interval.

Similarly, you can use the Unicorn Binance WebSocket API to subscribe to WebSocket streams and retrieve real-time data:

from unicorn_binance_websocket_api import BinanceWebSocketApiManager  
  
ubwa = BinanceWebSocketApiManager(exchange="binance.com")  
ubwa.create_stream(channels='kline_1h', markets='BTCUSDT')  
  
while True:  
    klines = ubwa.pop_stream_data_from_stream_buffer()  
    if klines:  
        print(klines)

This example creates a WebSocket stream for klines data with a 1-hour interval for the BTCUSDT trading pair.

When using the Unicorn Binance Websocket API to download data from Binance, it’s important to keep in mind that the first data packet you receive will always be {"result": null, "id": 1}. This is Binance's way of acknowledging that your subscription request was successful. After that, you’ll start receiving the actual data packets that you subscribed to.

In summary, if you’re looking to download data from Binance using Python, you can use either the REST API or the WebSocket API. The Unicorn Binance Suite provides a comprehensive Python library for interacting with the Binance API, with sub modules for both REST and WebSocket APIs, making it easy to get started with downloading data from Binance.

To connect to other Binance exchanges just change the exchange string:
Binance: binance.com
Binance Testnet: binance.com-testnet
Binance Margin: binance.com-margin
Binance Margin Testnet: binance.com-margin-testnet
Binance Isolated Margin: binance.com-isolated_margin
Binance Isolated Margin Testnet: binance.com-isolated_margin-testnet Binance USD-M Futures: binance.com-futures
Binance USD-M Futures Testnet: binance.com-futures-testnet
Binance Coin-M Futures: binance.com-coin_futures
Binance US: binance.us
Binance TR: trbinance.com

You can find the documentations here:
https://oliver-zehentleitner.github.io/unicorn-binance-rest-api/
https://oliver-zehentleitner.github.io/unicorn-binance-websocket-api/

I hope you found this tutorial informative and enjoyable!

Thank you for reading, and happy coding!

Image source: https://pixabay.com

I won’t go into why CONDA-FORGE and what’s great about Anaconda and the alternative package manager.

There are several ways, here is described the easiest and most modern way with grayskull .

Basically publishing a package only takes about 15 minutes if you know how!

First, some quick info:

Anyone can publish a PyPi package on CONDA-FORGE, you don’t have to be connected in any way to the project you want to publish.

You need a GitHub account and an installed Python.

The PyPi package must be available as a source package (SDIST) and not as a wheel on PyPi.

Here’s how:

1. The goal is to create a recipe. This is a file (meta.yaml) that contains all the information for CONDA-FORGE to automatically build a package. This recipe can be created automatically by the tool grayskull. So we start with the installation of grayskull either with pip or conda as described here: https://github.com/conda-incubator/grayskull#installation.

2. Once grayskull is installed, the command grayskull pypi <pypi-package-name> creates a recipe from the PyPi package, which can be submitted to CONDA-FORGE.
If this command throws the error AttributeError: Hash information for sdis was not found on PyPi metadata., then the PyPi package is not available as source distribution but probably only as wheel. A SDIST package can be created with the command python3 setup.py sdist and can be combined with the creation of a wheel: python3 setup.py bdist_wheel sdist

3. Once the recipe (meta.yaml) is created, please open and check it:

The maintainer name must match your github username.

In the about:sector change the url in home: to the project website and add below:
dev_url: https://github.com/you/repo
doc_url: https://you.github.io/repo

4. Create a fork of https://github.com/conda-forge/staged-recipes

5. Create a separate branch of the staged-recipes repository on Github for each recipe you want to submit.

6. Add a folder with the name of your package to the respective branch in the folder recipes and add the created meta.yamland start a pull request.
Read the comments for writing the pull request, check all the checkboxes and do what they ask for.

8. All CI checks of the PR should be successful. If so, create a new post with the content @conda-forge/staged-recipes, ready for review and @conda-forge-admin, please ping team. This triggers the editing process by the CONDA-FORGE team.

9. Wait for email messages and join the team on Github.

10. On each new PyPi release a bot opens a PR on the feedstock repository and you have to merge it manually to trigger the creation of a new package for conda. To make this automatically just add @conda-forge-admin, please add bot automerge.

Chat for support: https://gitter.im/conda-forge/conda-forge.github.io

I hope you found this tutorial informative and enjoyable! Don’t forget to follow me on Medium, Twitter, GitHub, and LinkedIn to stay updated on my latest releases and insights. If you found this article helpful, please hit that applause 👏 button to show your support! Your constructive feedback is always appreciated as it helps me improve the quality of my content.

Thank you for reading, and happy coding!

The main reason: Medium blocks AI crawlers by default — no opt-in, no opt-out, no per-author control. In 2026, AI assistants are becoming a primary discovery channel for technical content. If Claude or ChatGPT can't read my articles, I'm invisible to a growing part of my potential audience. And that's a decision Medium made for me, not with me.

On Hashnode with my own domain, I control the robots.txt. My content can be indexed, read, and recommended by AI assistants. That's exactly what I want.

All existing articles will be migrated from Medium shortly. The new URL is https://blog.technopathy.club/.

If you've been following me on Medium — welcome to the new home.