why i got a response 503 code？

[plaxkk]

[RealDarkCraft]

DeepL's anti-bot detection i guess

[danny900714]

Is this issue investigated or not?

[RealDarkCraft]

Is this issue investigated or not?

I don't know, and btw DeepL web client dosent use the REST api anymore, now it use : SignalR (websocket) + MessagePack + Protocol Buffers

[missuo]

Fixed in v1.2.0 / v1.2.1.

The HTTP 503 you were hitting came from the upstream backend (www2.deepl.com/jsonrpc) rate-limiting your IP — DeepL has tightened that endpoint to the point where any single IP gets HTTP 429 code 1042911 Too many requests within a handful of free-tier calls.

We migrated to the oneshot endpoint (oneshot-free.www.deepl.com/v1/translate) that the official Chrome extension uses. It lives on a separate rate-limit pool and accepts anonymous traffic with a literal Authorization: None header. Details and request-byte alignment in #217.

Please update to v1.2.1 — if you're on Docker:

docker pull ghcr.io/owo-network/deeplx:latest
docker compose up -d

Closing.