TEN-framework / TEN-framework/ten-framework

[BUG] Not in green status

Open
#1,765 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.1k
Forks
1.4k
Avg merge
2d 15m
Merged PRs (30d)
22

Description

Description

After a normal startup, http:/localhost:3000 can be accessed, but it cannot be used normally. A ❌️ is displayed on the top right corner, but accessing http:/localhost:49483 allows normal use.

Environment

docker

Steps to reproduce

root@7633b73412ab:/app/agents/examples/http-control# task run
task: [run-api-server] ./bin/api -tenapp_dir=/app/agents/examples/http-control/tenapp
task: [run-gd-server] tman designer
task: [run-frontend] bun run dev
$ next dev --turbopack
2025/11/18 09:02:37 WARN load .env file failed err="open .env: no such file or directory"
2025/11/18 09:02:37 INFO Server configured with tenapp_dir tenappDir=/app/agents/examples/http-control/tenapp
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

  • using env: export GIN_MODE=release
  • using code: gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET / --> app/internal.(*HttpServer).handlerHealth-fm (4 handlers)
[GIN-debug] GET /health --> app/internal.(*HttpServer).handlerHealth-fm (4 handlers)
[GIN-debug] GET /list --> app/internal.(*HttpServer).handlerList-fm (4 handlers)
[GIN-debug] POST /start --> app/internal.(*HttpServer).handlerStart-fm (4 handlers)
[GIN-debug] POST /stop --> app/internal.(*HttpServer).handlerStop-fm (4 handlers)
[GIN-debug] POST /ping --> app/internal.(*HttpServer).handlerPing-fm (4 handlers)
[GIN-debug] GET /graphs --> app/internal.(*HttpServer).handleGraphs-fm (4 handlers)
[GIN-debug] GET /dev-tmp/addons/default-properties --> app/internal.(*HttpServer).handleAddonDefaultProperties-fm (4 handlers)
[GIN-debug] POST /token/generate --> app/internal.(*HttpServer).handlerGenerateToken-fm (4 handlers)
[GIN-debug] GET /vector/document/preset/list --> app/internal.(*HttpServer).handlerVectorDocumentPresetList-fm (4 handlers)
[GIN-debug] POST /vector/document/update --> app/internal.(*HttpServer).handlerVectorDocumentUpdate-fm (4 handlers)
[GIN-debug] POST /vector/document/upload --> app/internal.(*HttpServer).handlerVectorDocumentUpload-fm (4 handlers)
2025/11/18 09:02:37 INFO server start port=8080 service=HTTP_SERVER
[GIN-debug] [WARNING] You trusted all proxies, this is NOT safe. We recommend you to set a value.
Please check https://pkg.go.dev/github.com/gin-gonic/gin#readme-don-t-trust-all-proxies for details.
[GIN-debug] Listening and serving HTTP on :8080
! Doesn't specify the base directory, use current working directory instead: /app/agents/examples/http-control/tenapp
:-) Starting server at http://0.0.0.0:49483
▲ Next.js 16.0.1 (Turbopack)

✓ Starting...
✓ Ready in 875ms
○ Compiling / ...

Expected behavior

green status

Severity

Critical

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running task run in agents/examples/http-control and compare the frontend at http://localhost:3000 with the working server at http://localhost:49483. Use the logged Next.js startup and the API entry point bin/api to trace why the frontend shows a failed status; done means normal use at port 3000 with a green status indicator.

Written by the indexing model from the issue text.

Assessment

Tech stack
bun, docker, next.js
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.