🚨 Bug: Dify Self-Hosted install page returns 404 on /console/api/setup (HTTPS enabled)

[50ethan]

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．4．１

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Self Checks

• I have searched existing issues
• I am reporting a bug, not asking a question
• I am using English

---

Dify version

1.4.1 (Self-hosted via Docker)

Deployment type

Self-hosted VPS (ConoHa)

---

Problem description

After successfully setting up SSL (HTTPS) and accessing https://sora-chat.shop/install, the UI loads but the API call to:
GET https://sora-chat.shop/console/api/setup

returns 404 Not Found, and browser shows:

SyntaxError: Unexpected token '<', "<!doctype "... is not valid JSON

This causes the install screen to freeze.

---

What I tried

• Confirmed that API container is running and accessible on http://api:5001
• NEXT_PUBLIC_API_PREFIX=https://sora-chat.shop/api is correctly passed to the web container
• All volumes and environment variables are aligned per official instructions
• docker-compose.yml, default.conf, and .env are configured as per https guide

---

Screenshot

← GitHubに画像アップ後、リンク差し替えてください

---

Logs

• docker compose logs api shows API is booting successfully
• docker compose logs nginx shows Nginx is routing

---

Request

Please clarify:

• Should the frontend be calling /console/api/setup?
• If yes, how should default.conf be configured to route this properly?

Thank you!

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot]

Yes, the frontend should call /console/api/setup during the self-hosted install process. The backend exposes this endpoint using Flask Blueprints, and the Nginx config template for Dify includes a location block that should proxy /console/api requests to http://api:5001. Here’s the relevant section from the default Nginx config:

location /console/api {
  proxy_pass http://api:5001;
  include proxy.conf;
}

If you’re getting a 404, double-check that your live Nginx config matches this pattern and that the API container is healthy. Also, make sure there are no typos or extra path segments in your proxy rules. The /setup endpoint is registered under /console/api/setup for self-hosted installs and should return JSON with the setup status if routed correctly. If you see an HTML response (like a doctype), it usually means the request is being routed to the frontend instead of the API backend, which points to a proxy misconfiguration.

You can review the Nginx config template here:
default.conf.template
And see the backend endpoint registration here:
setup.py
console/init.py

If your config matches and you still get a 404, try reloading Nginx and confirm that the API container is reachable from the Nginx container.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[50ethan]

@dosu

Thank you for the detailed explanation.

I understand now. It's highly likely that the issue is with my Nginx proxy configuration sending requests to the frontend instead of the API.

I will check the points you've pointed out:

Comparing my live Nginx configuration with the template.
Ensuring the API container is healthy and running correctly.
Checking the path for any typos.
The tip that receiving an HTML response instead of JSON is a key indicator of a proxy misconfiguration was also very helpful.

I will investigate this immediately and report back with the results.

[dosubot]

You're welcome! If you run into any more issues or have questions after checking your config, just let me know. Happy to help!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}