dify 1.0-beta get error message : line 1 column1 (char0)

[Patrick-Woo]

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.0-beta

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I directly download the 1.0 beta repo and then perform docker compose up to make the dify imgs download and up. after I enter the dify/app web page, I get the error "line1 comun1 (char0)" all the time.

✔️ Expected Behavior

I have three questions:

1. how to install 1.0 beta from scratch(not update)?
2. how to solve the line1 column1(char0) error?
3. is the beta ready for use?

❌ Actual Behavior

No response

[dosubot]

Hello @Patrick-Woo! I'm here to help you with any issues, bugs, or questions you have regarding Dify. I can assist with troubleshooting, providing solutions, and guiding you to become a contributor. Let's work together to resolve your issue.

I found a similar closed issue related to JSON parsing errors, specifically "SyntaxError: Unterminated string in JSON at position 50," but no solution was found in the comments ^[1].

For your questions:

1. Installation from Scratch: To install Dify 1.0-beta from scratch, follow these steps:

   • Fork and clone the Dify repository.
   • Ensure dependencies like Docker, Docker Compose, Node.js, npm or Yarn, and Python are installed.
   • Install the backend and frontend by navigating to their respective directories and following the README instructions.
   • Access Dify via your browser to verify the setup. More detailed steps can be found in the installation guide ^[2].

2. Solving the JSON Parsing Error: The error "Expecting value: line 1 column 1 (char 0)" typically indicates an issue with an empty or malformed JSON input. Ensure that your JSON payload is correctly formatted. For example:

   {
     "token": "EAA25127B638EBE05A4D35561F7CF2FE"
   }

   Make sure the JSON is not empty and follows proper syntax ^[3].

3. Beta Readiness for Use: I couldn't find specific documentation on the stability and readiness of the Dify 1.0-beta version for production use. It might be beneficial to test thoroughly in a development environment before deploying to production.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[crazywoola]

Please follow the https://github.com/langgenius/dify/releases/tag/1.0.0-beta.1 to install it.
For questions, please use discussion instead.

[Patrick-Woo]

Please follow the https://github.com/langgenius/dify/releases/tag/1.0.0-beta.1 to install it. For questions, please use discussion instead.

@crazywoola
hi there, I strictly follow the installation guide to install beta 1.0, however the issue is remaining. please help to recheck my installation steps and correct me if I am wrong. thx a lot.

1.installation steps:
1). git clone https://github.com/langgenius/dify.git (version 0.15.1 code)
2). git checkout 1.0.0-beta.1
3). cd ./docker
4) ./generate_docker_compose
5). docker compose -f docker-compose.yaml up -d

all the steps are fine without any error.

2. errors when log in the local dify webpage
   1)http://192.168.163.128/apps
   error: line 1 column1 (char0)

2. http://192.168.163.128/explore/apps
   error:404 page not found

3)http://192.168.163.128/plugins
error: stunck and loading all the time.

3. docker compose ps result is as follows:
   NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
   docker-api-1 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" api 2 hours ago Up 2 hours 5001/tcp
   docker-db-1 postgres:15-alpine "docker-entrypoint.s…" db 2 hours ago Up 2 hours (healthy) 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp
   docker-nginx-1 nginx:latest "sh -c 'cp /docker-e…" nginx 2 hours ago Up 2 hours 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp
   docker-plugin_daemon-1 langgenius/dify-plugin-daemon:0.0.1-local "/bin/bash -c /app/e…" plugin_daemon 2 hours ago Up 2 hours 0.0.0.0:5003->5003/tcp, :::5003->5003/tcp
   docker-redis-1 redis:6-alpine "docker-entrypoint.s…" redis 2 hours ago Up 2 hours (healthy) 6379/tcp
   docker-sandbox-1 langgenius/dify-sandbox:0.2.10 "/main" sandbox 2 hours ago Up 2 hours (healthy)
   docker-ssrf_proxy-1 ubuntu/squid:latest "sh -c 'cp /docker-e…" ssrf_proxy 2 hours ago Up 2 hours 3128/tcp
   docker-web-1 langgenius/dify-web:1.0.0-beta.1 "/bin/sh ./entrypoin…" web 2 hours ago Up 2 hours 3000/tcp
   docker-worker-1 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" worker 2 hours ago Up 2 hours 5001/tcp

[Ynewtime]

Same issue here