Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal Server Error #12664

Closed
5 tasks done
WeiMwww opened this issue Jan 13, 2025 · 19 comments
Closed
5 tasks done

Internal Server Error #12664

WeiMwww opened this issue Jan 13, 2025 · 19 comments
Labels
🐞 bug Something isn't working

Comments

@WeiMwww
Copy link

WeiMwww commented Jan 13, 2025

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.0-beta.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. According to. env. example, only the port number of nginx was modified;
  2. Modified the mounting directory and deleted unused databases according to docker-compose.yaml;
  3. After deployment, an "Internal Server Error" error is displayed;
  4. Check the logs, mainly for the "Plugin Daemon Service" issue.

Please tell me how to solve it? thank you

Best wishes
image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Jan 13, 2025
Copy link

dosubot bot commented Jan 13, 2025

To resolve the "Internal Server Error" related to the "Plugin Daemon Service" when deploying a self-hosted Dify version 1.0.0-beta.1 using Docker, you need to address the DNS resolution issue. This error often occurs because the system cannot resolve the hostname 'plugin', which might be due to marketplace.dify.ai being blocked by the Great Firewall (GFW). To fix this, ensure proper access to marketplace.dify.ai, possibly by using a VPN or configuring appropriate DNS settings to bypass GFW restrictions [1].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@WeiMwww
Copy link
Author

WeiMwww commented Jan 13, 2025 via email

@crazywoola crazywoola added this to the 1.0 milestone Jan 13, 2025
@hsoftxl
Copy link

hsoftxl commented Jan 14, 2025

same error

@hsoftxl
Copy link

hsoftxl commented Jan 14, 2025

mac studio m2 ultra , sequoia

@WeiMwww
Copy link
Author

WeiMwww commented Jan 14, 2025

要解决在使用 Docker 部署自托管 Dify 版本 1.0.0-beta.1 时与“Plugin Daemon Service”相关的“Internal Server Error”,您需要解决 DNS 解析问题。此错误通常是因为系统无法解析主机名 'plugin',这可能是由于 marketplace.dify.ai 被防火墙 (GFW) 阻止。要解决此问题,请确保正确访问 marketplace.dify.ai,可能通过使用 VPN 或配置适当的 DNS 设置来绕过 GFW 限制[1].

要继续与 Dosu 交谈,请提及 。

帮助 Dosu 学习!给它反馈:伟大的回应 |无关紧要的答案 |不正确的来源 |太冗长 |幻觉 |其他

I have resolved the 'Internal Server Error', but was reminded of the error 'Expecting value: line 1 column 1 (char 0)'.
It can be deployed without error prompts in 0.15.0, but errors have been consistently occurring in v1.0.0 beta. 1 version.

@WeiMwww
Copy link
Author

WeiMwww commented Jan 14, 2025

same error

I solved the 'Internal Server Error' by adding VPN proxies such as' http_dexy 'and' https_proxy ', but I also encountered other new errors.

@wopincm
Copy link

wopincm commented Jan 14, 2025

similar error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/api/core/plugin/manager/base.py", line 63, in _request
    response = requests.request(
               ^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin', port=5002): Max retries exceeded with url: /plugin/77a4d967-ab12-4026-aea0-55a64e6d21f6/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7fac4a2c9f70>: Failed to resolve 'plugin' ([Errno -2] Name or service not known)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask_restful/__init__.py", line 489, in wrapper
    resp = resource(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view
    return current_app.ensure_sync(self.dispatch_request)(**kwargs)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask_restful/__init__.py", line 604, in dispatch_request
    resp = meth(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/wraps.py", line 147, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/libs/login.py", line 94, in decorated_view
    return current_app.ensure_sync(func)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/wraps.py", line 27, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/workspace/__init__.py", line 32, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/workspace/plugin.py", line 274, in get
    {"tasks": PluginService.fetch_install_tasks(tenant_id, args["page"], args["page_size"])}
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/services/plugin/plugin_service.py", line 99, in fetch_install_tasks
    return manager.fetch_plugin_installation_tasks(tenant_id, page, page_size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/plugin.py", line 105, in fetch_plugin_installation_tasks
    return self._request_with_plugin_daemon_response(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/base.py", line 138, in _request_with_plugin_daemon_response
    response = self._request(method, path, headers, data, params, files)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/base.py", line 68, in _request
    raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
core.plugin.entities.plugin_daemon.PluginDaemonInnerError
2025-01-14 09:56:30,407.407 DEBUG [Dummy-7] [connectionpool.py:241] - Starting new HTTP connection (1): plugin:5002
2025-01-14 09:56:30,454.454 ERROR [Dummy-7] [base.py:67] - Request to Plugin Daemon Service failed
Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/_socketcommon.py", line 221, in getaddrinfo
    addrlist = get_hub().resolver.getaddrinfo(host, port, family, type, proto, flags)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/resolver/thread.py", line 63, in getaddrinfo
    return self.pool.apply(_socket.getaddrinfo, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/pool.py", line 161, in apply
    return self.spawn(func, *args, **kwds).get()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "src/gevent/event.py", line 330, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 360, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 348, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 328, in gevent._gevent_cevent.AsyncResult._raise_exception
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/_compat.py", line 50, in reraise
    raise value.with_traceback(tb)
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/threadpool.py", line 173, in __run_task
    thread_result.set(func(*args, **kwargs))
    ^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -2] Name or service not known

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    response = self._make_request(
               ^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connectionpool.py", line 493, in _make_request
    conn.request(
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 445, in request
    self.endheaders()
  File "/usr/local/lib/python3.12/http/client.py", line 1331, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.12/http/client.py", line 1091, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.12/http/client.py", line 1035, in send
    self.connect()
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 276, in connect
    self.sock = self._new_conn()
                ^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 205, in _new_conn
    raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7fac492712b0>: Failed to resolve 'plugin' ([Errno -2] Name or service not known)

@SimonPP123
Copy link

Hi, I have the following problem:
[openai] Error: PluginDaemonInternalServerError: killed by timeout
Always stops at 240 seconds.
I am using docker. Where can I push a bigger timeout limit?

@ljy-110
Copy link

ljy-110 commented Jan 21, 2025

After pulling the image, the front-end page opens with an Internal Server Error

Has the problem been solved

Image

@thinkinds
Copy link

After pulling the image, the front-end page opens with an Internal Server Error

Has the problem been solved

Image

suffering the same problem even after reverting to version 0.15.1 of Dify, local docker deployment

@brmysss
Copy link

brmysss commented Jan 23, 2025

I also encountered the same issue

@ljy-110
Copy link

ljy-110 commented Jan 23, 2025

I also encountered the same issue

我解决了,重新修改了docker的镜像,registry-mirrors,就可以拉取了。I solved it and re-modified the docker mirror, registry-mirrors, so it can be pulled.

@brmysss
Copy link

brmysss commented Jan 23, 2025

I also encountered the same issue我也遇到了同样的问题

我解决了,重新修改了docker的镜像,registry-mirrors,就可以拉取了。I solved it 和 re-modified the docker mirror, registry-mirrors, so it can be pulled.我解决了,重新修改了 docker 的镜像,registry-mirrors,就可以拉取了。I solved it 和 re-modified the docker mirror, registry-mirrors, so it can be pulled.

具体是怎么操作的呀?

@ljy-110
Copy link

ljy-110 commented Jan 23, 2025

I also encountered the same issue我也遇到了同样的问题

我解决了,重新修改了docker的镜像,registry-mirrors,就可以拉取了。I solved it 和 re-modified the docker mirror, registry-mirrors, so it can be pulled.我解决了,重新修改了 docker 的镜像,registry-mirrors,就可以拉取了。I solved it 和 re-modified the docker mirror, registry-mirrors, so it can be pulled.

具体是怎么操作的呀?

Image
"registry-mirrors": [
"https://docker.registry.cyou",
"https://registry.docker-cn.com",
"https://docker-cf.registry.cyou",
"https://dockercf.jsdelivr.fyi",
"https://docker.jsdelivr.fyi",
"https://dockertest.jsdelivr.fyi",
"https://mirror.aliyuncs.com",
"https://dockerproxy.com",
"https://mirror.baidubce.com",
"https://docker.m.daocloud.io",
"https://docker.nju.edu.cn",
"https://docker.mirrors.sjtug.sjtu.edu.cn",
"https://docker.mirrors.ustc.edu.cn",
"https://mirror.iscas.ac.cn",
"https://docker.rainbond.cc"
]

@brmysss
Copy link

brmysss commented Jan 23, 2025

same error  相同错误

I solved the 'Internal Server Error' by adding VPN proxies such as' http_dexy 'and' https_proxy ', but I also encountered other new errors.我通过添加 VPN 代理(如'http_proxy'和'https_proxy')解决了'Internal Server Error',但也遇到了其他新的错误。

你是添加在哪里的?

@BorisPolonsky
Copy link
Contributor

BorisPolonsky commented Jan 30, 2025

similar error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/api/core/plugin/manager/base.py", line 63, in _request
    response = requests.request(
               ^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='plugin', port=5002): Max retries exceeded with url: /plugin/77a4d967-ab12-4026-aea0-55a64e6d21f6/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7fac4a2c9f70>: Failed to resolve 'plugin' ([Errno -2] Name or service not known)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask_restful/__init__.py", line 489, in wrapper
    resp = resource(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view
    return current_app.ensure_sync(self.dispatch_request)(**kwargs)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/flask_restful/__init__.py", line 604, in dispatch_request
    resp = meth(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/wraps.py", line 147, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/libs/login.py", line 94, in decorated_view
    return current_app.ensure_sync(func)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/wraps.py", line 27, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/workspace/__init__.py", line 32, in decorated
    return view(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/controllers/console/workspace/plugin.py", line 274, in get
    {"tasks": PluginService.fetch_install_tasks(tenant_id, args["page"], args["page_size"])}
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/services/plugin/plugin_service.py", line 99, in fetch_install_tasks
    return manager.fetch_plugin_installation_tasks(tenant_id, page, page_size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/plugin.py", line 105, in fetch_plugin_installation_tasks
    return self._request_with_plugin_daemon_response(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/base.py", line 138, in _request_with_plugin_daemon_response
    response = self._request(method, path, headers, data, params, files)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/manager/base.py", line 68, in _request
    raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
core.plugin.entities.plugin_daemon.PluginDaemonInnerError
2025-01-14 09:56:30,407.407 DEBUG [Dummy-7] [connectionpool.py:241] - Starting new HTTP connection (1): plugin:5002
2025-01-14 09:56:30,454.454 ERROR [Dummy-7] [base.py:67] - Request to Plugin Daemon Service failed
Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/_socketcommon.py", line 221, in getaddrinfo
    addrlist = get_hub().resolver.getaddrinfo(host, port, family, type, proto, flags)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/resolver/thread.py", line 63, in getaddrinfo
    return self.pool.apply(_socket.getaddrinfo, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/pool.py", line 161, in apply
    return self.spawn(func, *args, **kwds).get()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "src/gevent/event.py", line 330, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 360, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 348, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 328, in gevent._gevent_cevent.AsyncResult._raise_exception
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/_compat.py", line 50, in reraise
    raise value.with_traceback(tb)
  File "/app/api/.venv/lib/python3.12/site-packages/gevent/threadpool.py", line 173, in __run_task
    thread_result.set(func(*args, **kwargs))
    ^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -2] Name or service not known

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    response = self._make_request(
               ^^^^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connectionpool.py", line 493, in _make_request
    conn.request(
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 445, in request
    self.endheaders()
  File "/usr/local/lib/python3.12/http/client.py", line 1331, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.12/http/client.py", line 1091, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.12/http/client.py", line 1035, in send
    self.connect()
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 276, in connect
    self.sock = self._new_conn()
                ^^^^^^^^^^^^^^^^
  File "/app/api/.venv/lib/python3.12/site-packages/urllib3/connection.py", line 205, in _new_conn
    raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7fac492712b0>: Failed to resolve 'plugin' ([Errno -2] Name or service not known)

We've observed InternalServerError as well.

urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='plugin', port=5002): Max retries exceeded with url: /plugin/7fd607f0-9b5a-496b-b69f-3abf8f5920b4/management/install/tasks?page=1&page_size=100 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7fac988638f0>: Failed to resolve 'plugin' ([Errno -3] Temporary failure in name resolution)"))

Given the log from api, it appears that it's due to some possible hard-coded domain name for pluginDaemon. I tried searching fetch_plugin_installation_tasks but couldn't find this part in the entire langgenius organization.

@arsaboo
Copy link

arsaboo commented Mar 2, 2025

I am still seeing this error and I have pulled the latest images. Do we need to make any changes to the docker compose? I don't see any env variable for PLUGIN_DAEMON_KEY in my docker compose

@WeiMwww
Copy link
Author

WeiMwww commented Mar 2, 2025 via email

@polhel
Copy link

polhel commented Mar 12, 2025

How to fix ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests