INTERNAL_FILES_URL

[kingWYZ]

Self Checks

• 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.

Content

Can the INTERNAL_FILES_URL parameter use http://:?

[kingWYZ]

Can the INTERNAL_FILES_URL parameter use http://ip:port?

[dosubot[bot]]

Yes, INTERNAL_FILES_URL can use the http://<ip>:<port> format.

• FILES_URL — used for external/frontend access. Set it to something like http://<your-server-ip>:5001.
• INTERNAL_FILES_URL — used for internal (container-to-container) communication. The default in Docker deployments is http://api:5001, but you can replace it with http://<ip>:<port> (e.g., http://192.168.1.100:5001) if your setup requires it [1].

Both variables just need a valid URL with the http:// or https:// protocol prefix. Example in your .env:

FILES_URL=http://<your-public-ip>:5001
INTERNAL_FILES_URL=http://<internal-ip>:5001

After changing these, restart your containers with docker compose down && docker compose up -d.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[kingWYZ]

So I should use http://api:5001, rather than keeping it consistent with FILES_URL, right?

[dosubot[bot]]

It depends on your deployment setup:

• If you're using Docker Compose (the standard setup), then yes — use http://api:5001 for INTERNAL_FILES_URL. This allows internal services (like the plugin daemon) to reach the API container directly over the Docker network without going through your external IP/domain [1].

• If you're running services outside Docker (e.g., bare-metal or all services on the same host), you can set INTERNAL_FILES_URL to the same value as FILES_URL, or simply leave it unset — it automatically falls back to FILES_URL [2].

So in a typical Docker Compose deployment:

FILES_URL=http://<your-public-ip>:5001        # for browsers/external access
INTERNAL_FILES_URL=http://api:5001             # for container-to-container access

They serve different purposes — FILES_URL is what external clients (browsers, LLMs) use, while INTERNAL_FILES_URL is what internal services use to talk to the API container directly on the Docker network.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.