After deploying dify 1.15.0, the frontend throws errors, please refer to the screenshot.

[shouhuzhe]

Self Checks

• I have read the Contributing Guide and Language Policy.
• 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, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.15.0

Cloud or Self Hosted

Cloud

Steps to reproduce

✔️ Expected Behavior

After deploying dify 1.15.0, the frontend throws errors, please refer to the screenshot.

❌ Actual Behavior

After deploying dify 1.15.0, the frontend throws errors, please refer to the screenshot.

[dosubot]

I wasn't able to view your screenshot, but several frontend issues have been reported and fixed since the v1.15.0 release on June 25. Here are the most common ones:

Common frontend errors in 1.15.0:

1. Published web app redirecting to login page — the useTimestamp() hook was incorrectly calling a console API endpoint from public pages, triggering auth redirects. Fixed in PR feat(agent-v2): sync nightly updates to main (2026-06-25) #37915 [1].

2. Toast notification bug — clicking toasts during fade-out could leave invisible fragments blocking UI interactions [2].

3. SSE error handler masking network failures — a TypeError in the error handler could prevent proper error reporting to the user [3].

4. Deployment page hydration issue — router hook timing issues causing unreliable state [4].

5. Workflow tracing not updating — duplicate tracing rows appeared when the node index was 0. Fixed in PR fix(web): update workflow tracing when match index is 0 #38096 [5].

Recommended steps:

1. Make sure database migrations completed successfully:

   docker compose exec api flask upgrade-db

2. Pull the latest images / update to the newest patch — most of these issues have been fixed in commits after the initial release.

3. If you're running in dev mode, clear the .next cache folder.

Could you share which specific error message you're seeing (text rather than screenshot if possible)? That would help narrow down which of the above issues you're hitting.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[shouhuzhe]

The screenshot shows an error occurring during K8s deployment. The error pops up immediately upon startup, even before any frontend access attempts.

[shouhuzhe]

Please help check and confirm how to resolve this issue.

[dosubot]

Without being able to see the actual error text, I can point to the most common causes of immediate startup failures in Dify 1.15.0 K8s deployments:

1. File storage / migration issues — The API container throws FileNotFoundError immediately if database records reference files that don't exist on disk. This is the most commonly reported "error on startup" in 1.15.0 [1]. Fix: ensure the database migration ran to completion and run the orphaned file cleanup:

   kubectl exec -it <api-pod> -- /app/api/.venv/bin/flask upgrade-db
   kubectl exec -it <api-pod> -- /app/api/.venv/bin/flask clear-orphaned-file-records

2. Missing init_permissions service — 1.15.0 requires a new initialization step for storage permissions. If your K8s manifests were adapted from an older version, you may be missing this [1].

3. Environment variable issues — Make sure all required env vars (especially APP_WEB_URL, storage-related vars like OPENDAL_FS_ROOT, and MIGRATION_ENABLED=true) are set correctly in your K8s ConfigMap/Secrets.

4. SSRF proxy deny-by-default — If your app calls external services during initialization, the new strict SSRF proxy will block them with 403 Forbidden unless you explicitly whitelist domains via SSRF_PROXY_ALLOW_PRIVATE_DOMAINS [2].

To help narrow this down further, could you share:

• The pod logs from the failing container (kubectl logs <pod-name>)
• Which container is failing — the web (Next.js frontend) or the api (Flask backend)?
• What version you upgraded from?

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[shouhuzhe]

Deployment of Dify v1.14.2 went smoothly, but issues emerged with v1.15.0. These are two separate newly-deployed environments with completely rebuilt databases and file storage, so they do not interfere with one another. Both flask db upgrade and flask backfill-plugin-auto-upgrade executed successfully.Could you please check whether there are any newly added mandatory configurations required for Dify v1.15.0, and help locate and confirm the root cause of the issue?

[dosubot]

I investigated the configuration differences between v1.14.2 and v1.15.0. Here's what I found:

No new mandatory environment variables were introduced — all new variables have default values [1] [2]. However, there are some important changes:

Removed variables (could cause issues if your manifests still reference them):

• ALLOW_INLINE_STYLES
• SSRF_REVERSE_PROXY_PORT
• SSRF_SANDBOX_HOST
• SANDBOX_PORT

New variable to note for the web container:

• SERVER_CONSOLE_API_URL — defaults to http://api:5001, used for internal server-side communication from the web container to the API . If your K8s service names differ from api, this may need to be set explicitly.

SSRF proxy changes: The proxy now uses a deny-by-default policy. If your app calls external or private services, you may need to set SSRF_PROXY_ALLOW_PRIVATE_IPS and SSRF_PROXY_ALLOW_PRIVATE_DOMAINS.

Known frontend bug in v1.15.0: Published web apps redirect to login due to an unauthorized call to /console/api/account/profile from the useTimestamp() hook. This was fixed in PR #37915 [3].

That said, I haven't found reports of the web container crashing on startup in fresh 1.15.0 deployments. The issue you're experiencing may be specific to your K8s configuration. Could you share:

1. The actual error message/logs from the failing pod (kubectl logs <web-pod>)
2. Whether it's the web or api pod that's failing
3. Your environment variables for the web container (especially anything URL-related like CONSOLE_API_URL, APP_WEB_URL, SERVER_CONSOLE_API_URL)

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[shouhuzhe]

The dify-web container v1.15.0 cannot start successfully on K8s; errors are reported immediately upon launch.

[dosubot]

A major architectural change between v1.14.2 and v1.15.0 is the complete removal of PM2 from the web container [1]. This could be why it worked in v1.14.2 but fails in v1.15.0:

• Before (v1.14.2): Startup command was pm2 start /app/web/server.js -i ${PM2_INSTANCES}
• After (v1.15.0): Direct execution with node /app/targets/next/web/server.js

The server.js path also changed from /app/web/server.js to /app/targets/next/web/server.js [2].

If your K8s deployment manifest overrides the container command or entrypoint (e.g., referencing the old PM2 startup or old path), this would cause an immediate startup failure. The container now relies on its built-in entrypoint.sh [3] which handles the correct startup sequence.

Check these in your K8s manifest:

1. Remove any custom command: or args: that reference PM2 or the old /app/web/server.js path
2. Remove the PM2_INSTANCES environment variable if set
3. Let the container use its default entrypoint

Without seeing your actual error logs, I can't confirm this is the cause. Could you please share the output of:

kubectl logs <dify-web-pod-name>

This will help pinpoint the exact failure.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[shouhuzhe]

The error shown in the screenshot is the raw printed log output.

[shouhuzhe]

[dosubot]

Now I can see the exact issue. The root cause is clear from the logs:

Error: getaddrinfo ENOTFOUND mydify1150.example.com

The web container is making server-side (SSR) API calls to your external hostname mydify1150.example.com, but the pod cannot resolve that hostname from inside the K8s cluster.

This is a new behavior in v1.15.0 — server-side rendering with API calls was introduced in this version [1], which is why v1.14.2 worked fine without this configuration.

Fix: Set the SERVER_CONSOLE_API_URL environment variable on the frontend (web) container to use the internal K8s service DNS name of the API service instead of the external domain:

frontend:
  envs:
    - name: SERVER_CONSOLE_API_URL
      value: "http://<your-dify-api-service-name>:5001"
    - name: MARKETPLACE_API_URL
      value: 'https://marketplace.dify.ai'
    - name: MARKETPLACE_URL
      value: 'https://marketplace.dify.ai'

Replace <your-dify-api-service-name> with the actual K8s service name for the API (e.g., dify-api, or the full DNS dify-api.<namespace>.svc.cluster.local). You can find it with kubectl get svc | grep api.

This variable tells the Next.js server where to send SSR requests internally [2] [3]. The official Docker Compose defaults it to http://api:5001 [4], but the douban Helm chart hasn't been updated for this v1.15.0 change yet.

The 401 Unauthorized errors in the log are a separate (expected) issue — the health probe hits /apps which triggers an unauthenticated SSR request to the API. Once SERVER_CONSOLE_API_URL is set correctly, these will resolve as non-fatal (the log already says [systemFeatures] fetch failed, using defaults).

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[shouhuzhe]

I have set the SERVER_CONSOLE_API_URL configuration to http://dify-api-svc.dify-test-1150.svc.cluster.local, which is the internal request address for containers. However, the same error still occurs. The error message is as follows:

2026-06-29T21:52:34.188249534+08:00 ▲ Next.js 16.2.9
2026-06-29T21:52:34.188475247+08:00 - Local: http://dify-frontend-8d5c94b6d-7787d:3000
2026-06-29T21:52:34.188481160+08:00 - Network: http://dify-frontend-8d5c94b6d-7787d:3000
2026-06-29T21:52:34.189136642+08:00 ✓ Ready in 0ms
2026-06-29T21:53:04.590942755+08:00 Error: Unauthorized
2026-06-29T21:53:04.590988328+08:00 at ignore-listed frames {
2026-06-29T21:53:04.590990776+08:00 defined: false,
2026-06-29T21:53:04.590992376+08:00 code: 'UNAUTHORIZED',
2026-06-29T21:53:04.590993880+08:00 status: 401,
2026-06-29T21:53:04.590995602+08:00 data: {
2026-06-29T21:53:04.590997170+08:00 body: {
2026-06-29T21:53:04.590998649+08:00 code: 'unauthorized',
2026-06-29T21:53:04.591000884+08:00 message: 'Invalid Authorization token.',
2026-06-29T21:53:04.591002302+08:00 status: 401
2026-06-29T21:53:04.591003734+08:00 },
2026-06-29T21:53:04.591005193+08:00 status: 401,
2026-06-29T21:53:04.591006628+08:00 headers: {
2026-06-29T21:53:04.591008083+08:00 'access-control-allow-credentials': 'true',
2026-06-29T21:53:04.591010121+08:00 'access-control-allow-origin': 'http://mydify1150.example.com/',
2026-06-29T21:53:04.591011555+08:00 'access-control-expose-headers': 'X-Env, X-Trace-Id, X-Version',
2026-06-29T21:53:04.591012980+08:00 'content-length': '78',
2026-06-29T21:53:04.591014842+08:00 'content-type': 'application/json',
2026-06-29T21:53:04.591016368+08:00 date: 'Mon, 29 Jun 2026 13:53:04 GMT',
2026-06-29T21:53:04.591017791+08:00 vary: 'Cookie',
2026-06-29T21:53:04.591019182+08:00 'www-authenticate': 'Bearer realm="api"',
2026-06-29T21:53:04.591020593+08:00 'x-env': 'PRODUCTION',
2026-06-29T21:53:04.591022024+08:00 'x-version': '1.15.0'
2026-06-29T21:53:04.591023511+08:00 }
2026-06-29T21:53:04.591024937+08:00 }
2026-06-29T21:53:04.591026355+08:00 }
2026-06-29T21:53:04.796684604+08:00 Error [NetworkError]: Request failed due to a network error: GET http://mydify1150.example.com/console/api/system-features
2026-06-29T21:53:04.796719204+08:00 at #d (.next/server/chunks/ssr/1lrm4_y..js:1:21876)
2026-06-29T21:53:04.796728451+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:04.796730983+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:04.796733231+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:04.796735392+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:04.796737587+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:04.796739787+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:04.796742325+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773)
2026-06-29T21:53:04.796744481+08:00 at async (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:1844) {
2026-06-29T21:53:04.796747041+08:00 request: Request {
2026-06-29T21:53:04.796749230+08:00 method: 'GET',
2026-06-29T21:53:04.796751817+08:00 url: 'http://mydify1150.example.com/console/api/system-features',
2026-06-29T21:53:04.796754261+08:00 headers: Headers { 'x-csrf-token': '' },
2026-06-29T21:53:04.796756595+08:00 destination: '',
2026-06-29T21:53:04.796759127+08:00 referrer: 'about:client',
2026-06-29T21:53:04.796761546+08:00 referrerPolicy: '',
2026-06-29T21:53:04.796763968+08:00 mode: 'cors',
2026-06-29T21:53:04.796766465+08:00 credentials: 'include',
2026-06-29T21:53:04.796768561+08:00 cache: 'default',
2026-06-29T21:53:04.796791449+08:00 redirect: 'manual',
2026-06-29T21:53:04.796793486+08:00 integrity: '',
2026-06-29T21:53:04.796795146+08:00 keepalive: false,
2026-06-29T21:53:04.796796728+08:00 isReloadNavigation: false,
2026-06-29T21:53:04.796798305+08:00 isHistoryNavigation: false,
2026-06-29T21:53:04.796799945+08:00 signal: AbortSignal { aborted: false }
2026-06-29T21:53:04.796801861+08:00 },
2026-06-29T21:53:04.796803573+08:00 [cause]: TypeError: fetch failed
2026-06-29T21:53:04.796805193+08:00 at async #d (.next/server/chunks/ssr/1lrm4_y..js:1:21450)
2026-06-29T21:53:04.796806771+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:04.796808298+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:04.796809855+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:04.796811410+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:04.796813012+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:04.796814595+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:04.796816138+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773) {
2026-06-29T21:53:04.796817754+08:00 [cause]: Error: getaddrinfo ENOTFOUND mydify1150.example.com
2026-06-29T21:53:04.796819338+08:00 at ignore-listed frames {
2026-06-29T21:53:04.796820901+08:00 errno: -3007,
2026-06-29T21:53:04.796822647+08:00 code: 'ENOTFOUND',
2026-06-29T21:53:04.796824192+08:00 syscall: 'getaddrinfo',
2026-06-29T21:53:04.796825852+08:00 hostname: 'mydify1150.example.com'
2026-06-29T21:53:04.796827565+08:00 }
2026-06-29T21:53:04.796829340+08:00 }
2026-06-29T21:53:04.796832720+08:00 }
2026-06-29T21:53:04.797429835+08:00 [systemFeatures] fetch failed, using defaults Error [NetworkError]: Request failed due to a network error: GET http://mydify1150.example.com/console/api/system-features
2026-06-29T21:53:04.797452022+08:00 at #d (.next/server/chunks/ssr/1lrm4_y..js:1:21876)
2026-06-29T21:53:04.797454240+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:04.797455590+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:04.797457051+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:04.797458389+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:04.797459658+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:04.797460923+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:04.797462860+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773)
2026-06-29T21:53:04.797464135+08:00 at async (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:1844) {
2026-06-29T21:53:04.797465595+08:00 request: Request {
2026-06-29T21:53:04.797466869+08:00 method: 'GET',
2026-06-29T21:53:04.797468461+08:00 url: 'http://mydify1150.example.com/console/api/system-features',
2026-06-29T21:53:04.797470061+08:00 headers: Headers { 'x-csrf-token': '' },
2026-06-29T21:53:04.797471351+08:00 destination: '',
2026-06-29T21:53:04.797473787+08:00 referrer: 'about:client',
2026-06-29T21:53:04.797475126+08:00 referrerPolicy: '',
2026-06-29T21:53:04.797476367+08:00 mode: 'cors',
2026-06-29T21:53:04.797477683+08:00 credentials: 'include',
2026-06-29T21:53:04.797479012+08:00 cache: 'default',
2026-06-29T21:53:04.797486444+08:00 redirect: 'manual',
2026-06-29T21:53:04.797487756+08:00 integrity: '',
2026-06-29T21:53:04.797489019+08:00 keepalive: false,
2026-06-29T21:53:04.797490278+08:00 isReloadNavigation: false,
2026-06-29T21:53:04.797504346+08:00 isHistoryNavigation: false,
2026-06-29T21:53:04.797505893+08:00 signal: AbortSignal { aborted: false }
2026-06-29T21:53:04.797507192+08:00 },
2026-06-29T21:53:04.797508554+08:00 [cause]: TypeError: fetch failed
2026-06-29T21:53:04.797509905+08:00 at async #d (.next/server/chunks/ssr/1lrm4_y..js:1:21450)
2026-06-29T21:53:04.797511171+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:04.797512448+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:04.797513790+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:04.797515135+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:04.797516605+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:04.797517875+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:04.797519130+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773) {
2026-06-29T21:53:04.797520464+08:00 [cause]: Error: getaddrinfo ENOTFOUND mydify1150.example.com
2026-06-29T21:53:04.797521757+08:00 at ignore-listed frames {
2026-06-29T21:53:04.797523042+08:00 errno: -3007,
2026-06-29T21:53:04.797524306+08:00 code: 'ENOTFOUND',
2026-06-29T21:53:04.797525563+08:00 syscall: 'getaddrinfo',
2026-06-29T21:53:04.797526895+08:00 hostname: 'mydify1150.example.com'
2026-06-29T21:53:04.797528241+08:00 }
2026-06-29T21:53:04.797529665+08:00 }
2026-06-29T21:53:04.797531019+08:00 }
2026-06-29T21:53:05.123665158+08:00 Error: Unauthorized
2026-06-29T21:53:05.123700056+08:00 at ignore-listed frames {
2026-06-29T21:53:05.123702081+08:00 defined: false,
2026-06-29T21:53:05.123703469+08:00 code: 'UNAUTHORIZED',
2026-06-29T21:53:05.123704820+08:00 status: 401,
2026-06-29T21:53:05.123706192+08:00 data: {
2026-06-29T21:53:05.123707692+08:00 body: {
2026-06-29T21:53:05.123709010+08:00 code: 'unauthorized',
2026-06-29T21:53:05.123710500+08:00 message: 'Invalid Authorization token.',
2026-06-29T21:53:05.123711771+08:00 status: 401
2026-06-29T21:53:05.123713065+08:00 },
2026-06-29T21:53:05.123714385+08:00 status: 401,
2026-06-29T21:53:05.123715674+08:00 headers: {
2026-06-29T21:53:05.123717164+08:00 'access-control-allow-credentials': 'true',
2026-06-29T21:53:05.123718783+08:00 'access-control-allow-origin': 'http://mydify1150.example.com/',
2026-06-29T21:53:05.123720224+08:00 'access-control-expose-headers': 'X-Env, X-Trace-Id, X-Version',
2026-06-29T21:53:05.123721522+08:00 'content-length': '78',
2026-06-29T21:53:05.123722776+08:00 'content-type': 'application/json',
2026-06-29T21:53:05.123724035+08:00 date: 'Mon, 29 Jun 2026 13:53:05 GMT',
2026-06-29T21:53:05.123725277+08:00 vary: 'Cookie',
2026-06-29T21:53:05.123726503+08:00 'www-authenticate': 'Bearer realm="api"',
2026-06-29T21:53:05.123727731+08:00 'x-env': 'PRODUCTION',
2026-06-29T21:53:05.123729012+08:00 'x-version': '1.15.0'
2026-06-29T21:53:05.123730297+08:00 }
2026-06-29T21:53:05.123731779+08:00 }
2026-06-29T21:53:05.123733056+08:00 }
2026-06-29T21:53:05.192338274+08:00 Error [NetworkError]: Request failed due to a network error: GET http://mydify1150.example.com/console/api/system-features
2026-06-29T21:53:05.192385133+08:00 at #d (.next/server/chunks/ssr/1lrm4_y..js:1:21876)
2026-06-29T21:53:05.192387469+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:05.192389123+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:05.192390488+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:05.192391827+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:05.192393148+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:05.192394489+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:05.192396135+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773)
2026-06-29T21:53:05.192397514+08:00 at async (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:1844) {
2026-06-29T21:53:05.192399223+08:00 request: Request {
2026-06-29T21:53:05.192400618+08:00 method: 'GET',
2026-06-29T21:53:05.192402258+08:00 url: 'http://mydify1150.example.com/console/api/system-features',
2026-06-29T21:53:05.192403731+08:00 headers: Headers { 'x-csrf-token': '' },
2026-06-29T21:53:05.192405082+08:00 destination: '',
2026-06-29T21:53:05.192407194+08:00 referrer: 'about:client',
2026-06-29T21:53:05.192408563+08:00 referrerPolicy: '',
2026-06-29T21:53:05.192409913+08:00 mode: 'cors',
2026-06-29T21:53:05.192411359+08:00 credentials: 'include',
2026-06-29T21:53:05.192412734+08:00 cache: 'default',
2026-06-29T21:53:05.192414092+08:00 redirect: 'manual',
2026-06-29T21:53:05.192415424+08:00 integrity: '',
2026-06-29T21:53:05.192416739+08:00 keepalive: false,
2026-06-29T21:53:05.192421540+08:00 isReloadNavigation: false,
2026-06-29T21:53:05.192422826+08:00 isHistoryNavigation: false,
2026-06-29T21:53:05.192424117+08:00 signal: AbortSignal { aborted: false }
2026-06-29T21:53:05.192425595+08:00 },
2026-06-29T21:53:05.192427132+08:00 [cause]: TypeError: fetch failed
2026-06-29T21:53:05.192428475+08:00 at async #d (.next/server/chunks/ssr/1lrm4_y..js:1:21450)
2026-06-29T21:53:05.192429773+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:05.192431066+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:05.192432539+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:05.192433814+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:05.192435119+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:05.192436387+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:05.192437700+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773) {
2026-06-29T21:53:05.192439032+08:00 [cause]: Error: getaddrinfo ENOTFOUND mydify1150.example.com
2026-06-29T21:53:05.192440317+08:00 at ignore-listed frames {
2026-06-29T21:53:05.192441597+08:00 errno: -3007,
2026-06-29T21:53:05.192442880+08:00 code: 'ENOTFOUND',
2026-06-29T21:53:05.192444180+08:00 syscall: 'getaddrinfo',
2026-06-29T21:53:05.192445476+08:00 hostname: 'mydify1150.example.com'
2026-06-29T21:53:05.192446828+08:00 }
2026-06-29T21:53:05.192448217+08:00 }
2026-06-29T21:53:05.192449585+08:00 }
2026-06-29T21:53:05.193039867+08:00 [systemFeatures] fetch failed, using defaults Error [NetworkError]: Request failed due to a network error: GET http://mydify1150.example.com/console/api/system-features
2026-06-29T21:53:05.193065410+08:00 at #d (.next/server/chunks/ssr/1lrm4_y..js:1:21876)
2026-06-29T21:53:05.193067682+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:05.193069242+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:05.193070697+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:05.193072225+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:05.193107162+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:05.193108954+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:05.193110860+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773)
2026-06-29T21:53:05.193112288+08:00 at async (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:1844) {
2026-06-29T21:53:05.193113935+08:00 request: Request {
2026-06-29T21:53:05.193355596+08:00 method: 'GET',
2026-06-29T21:53:05.193361131+08:00 url: 'http://mydify1150.example.com/console/api/system-features',
2026-06-29T21:53:05.193362947+08:00 headers: Headers { 'x-csrf-token': '' },
2026-06-29T21:53:05.193364407+08:00 destination: '',
2026-06-29T21:53:05.193366006+08:00 referrer: 'about:client',
2026-06-29T21:53:05.193367718+08:00 referrerPolicy: '',
2026-06-29T21:53:05.193369135+08:00 mode: 'cors',
2026-06-29T21:53:05.193370588+08:00 credentials: 'include',
2026-06-29T21:53:05.193371979+08:00 cache: 'default',
2026-06-29T21:53:05.193373361+08:00 redirect: 'manual',
2026-06-29T21:53:05.193374801+08:00 integrity: '',
2026-06-29T21:53:05.193376190+08:00 keepalive: false,
2026-06-29T21:53:05.193377591+08:00 isReloadNavigation: false,
2026-06-29T21:53:05.193379006+08:00 isHistoryNavigation: false,
2026-06-29T21:53:05.193380394+08:00 signal: AbortSignal { aborted: false }
2026-06-29T21:53:05.193381828+08:00 },
2026-06-29T21:53:05.193383330+08:00 [cause]: TypeError: fetch failed
2026-06-29T21:53:05.193384804+08:00 at async #d (.next/server/chunks/ssr/1lrm4_y..js:1:21450)
2026-06-29T21:53:05.193386246+08:00 at async #c (.next/server/chunks/ssr/1lrm4_y..js:1:20108)
2026-06-29T21:53:05.193387672+08:00 at async i (.next/server/chunks/ssr/1lrm4_y..js:1:11137)
2026-06-29T21:53:05.193389092+08:00 at async (.next/server/chunks/ssr/1lrm4_y..js:1:12234)
2026-06-29T21:53:05.193390541+08:00 at async as (.next/server/chunks/ssr/1lrm4_y..js:1:26485)
2026-06-29T21:53:05.193391976+08:00 at async g (.next/server/chunks/ssr/1lrm4_y..js:1:1999)
2026-06-29T21:53:05.193393396+08:00 at async aJ (.next/server/chunks/ssr/1lrm4_y..js:1:36641)
2026-06-29T21:53:05.193394792+08:00 at async $.call (.next/server/chunks/ssr/web_service_client_ts_116w1e4..js:9:6773) {
2026-06-29T21:53:05.193396195+08:00 [cause]: Error: getaddrinfo ENOTFOUND mydify1150.example.com
2026-06-29T21:53:05.193397635+08:00 at ignore-listed frames {
2026-06-29T21:53:05.193399056+08:00 errno: -3007,
2026-06-29T21:53:05.193423143+08:00 code: 'ENOTFOUND',
2026-06-29T21:53:05.193424796+08:00 syscall: 'getaddrinfo',
2026-06-29T21:53:05.193426303+08:00 hostname: 'mydify1150.example.com'
2026-06-29T21:53:05.193427818+08:00 }
2026-06-29T21:53:05.193429349+08:00 }
2026-06-29T21:53:05.193430790+08:00 }

[shouhuzhe]

Is this a normal error? Does it have any impact on the service itself?

[dosubot]

There are two separate issues in your logs, and they have different answers:

1. [systemFeatures] fetch failed, using defaults (ENOTFOUND for mydify1150.example.com)

This is a known bug in v1.15.0. The system-features call on certain routes is incorrectly using the external URL (CONSOLE_API_URL → mydify1150.example.com) instead of the internal SERVER_CONSOLE_API_URL you configured. The good news is: the app gracefully handles this failure — it falls back to built-in defaults [1] [2]. The service will still work, but some features may show as disabled (e.g., marketplace, social OAuth login) since the defaults are conservative.

2. Error: Unauthorized / Invalid Authorization token (401)

This is also a known regression bug in v1.15.0 [3]. Your liveness probe hits /apps, which triggers SSR. During SSR, the useTimestamp() hook incorrectly calls /console/api/account/profile — even though there's no logged-in session. The API correctly returns 401. This causes the page to redirect to /signin instead of rendering normally.

Both issues are fixed in PRs #38115 and #38116 [4] [5], merged June 28-29. These fixes should be included in the next patch release.

Impact on service:

• The systemFeatures failure is non-fatal (falls back to defaults), but you may notice some features appearing disabled.
• The 401 issue is more impactful — when users visit the console pages, they'll be redirected to /signin due to the broken SSR auth check. However, once logged in, the service should function normally.

Workaround until the patch is released: Downgrade only the web container to v1.14.2 while keeping your API/worker on v1.15.0:

frontend:
  image:
    tag: "1.14.2"

This avoids the SSR regressions since v1.14.2 didn't have server-side API calls [3].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.