Skip to content

Fix AI plugin callback URL port in Docker deployment#9739

Open
014-code wants to merge 1 commit into
jeecgboot:mainfrom
014-code:fix-ai-plugin-docker-base-url
Open

Fix AI plugin callback URL port in Docker deployment#9739
014-code wants to merge 1 commit into
jeecgboot:mainfrom
014-code:fix-ai-plugin-docker-base-url

Conversation

@014-code

@014-code 014-code commented Jul 1, 2026

Copy link
Copy Markdown

What Changed

This PR fixes an AI plugin invocation failure in Docker deployments when the MCP endpoint is not explicitly configured.

Previously, PluginToolBuilder used CommonUtils.getBaseUrl(request) as the fallback base URL. Behind Docker/nginx, this could produce:

http://jeecg-boot-system/jeecg-boot

When the MCP endpoint is empty, PluginToolBuilder falls back to
CommonUtils.getBaseUrl(request). In Docker reverse proxy deployment,
the request server port may be 80 while the actual application local
port is 8080, causing plugin calls to use jeecg-boot-system:80 and fail
with connection refused.

This change appends the internal local port only for single-label
internal hosts without an explicit port, keeping configured endpoints
and public domain URLs unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant