search

OwO-Network / DeepLX

Powerful Free DeepL API, No Token Required
https://ssa.sx/deeplx
MIT License
6.64k stars 532 forks source link

Error 503, "server gave HTTP response to HTTPS client", and EOF #137

Closed showgood163 closed 3 months ago

showgood163 commented 3 months ago

你好。

近期我在使用deeplx时发现，在连续多次成功（200）后，deeplx会报如下错误并停止翻译：

Aug 17 21:53:01 xxx bash[8959]: 2024/08/17 21:53:01 Post "https://www2.deepl.com/jsonrpc": http: server gave HTTP response to HTTPS client
Aug 17 21:53:01 xxx bash[8959]: [GIN] 2024/08/17 - 21:53:01 | 503 |  241.511939ms | yyy | POST     "/translate"
Aug 17 21:53:11 xxx bash[8959]: 2024/08/17 21:53:11 Post "https://www2.deepl.com/jsonrpc": http: server gave HTTP response to HTTPS client
Aug 17 21:53:11 xxx bash[8959]: [GIN] 2024/08/17 - 21:53:11 | 503 |  238.776021ms | yyy | POST     "/translate"

当然，类似的错误也可以是EOF

Aug 17 22:04:19 xxx bash[8959]: 2024/08/17 22:04:19 Post "https://www2.deepl.com/jsonrpc": EOF
Aug 17 22:04:19 xxx bash[8959]: [GIN] 2024/08/17 - 22:04:19 | 503 |  456.237782ms | yyy | POST     "/translate"
Aug 17 22:04:26 xxx bash[8959]: 2024/08/17 22:04:26 Post "https://www2.deepl.com/jsonrpc": http: server gave HTTP response to HTTPS client
Aug 17 22:04:26 xxx bash[8959]: [GIN] 2024/08/17 - 22:04:26 | 503 |  1.259129398s | yyy | POST     "/translate"

这错误也不是429。请问如果要排查这个问题该怎么做？

missuo commented 3 months ago

This situation may be a problem on the server side of DeepL, there is no solution, it may be that the server is overloaded.