Hey,

The document status remains in Queuing, I have already done numerous tests, but without success.

How can I resolve this problem?

I can't use this feature in your template, any tips to resolve this?

Will look into tonight, busy currently. Apologies for the delay.

thanks for the feedback!

Hey, apologies again and thanks for your patience. I’ve made an update to the template to include the Worker service (a copy of the Api service) with env MODE=api. However, it requires shared volumes between the Api and the Worker services, because you’ll end up getting a “File not found” error.

I’ve heard speculation around how it is possible, but not yet integrated in the UI, so I’m hopeful that it comes in the following weeks but unfortunately for now, don’t believe it’s something fixable for the meantime until we can get shared volumes.

If you do use an S3 storage bucket on the other hand, I don’t see any reason why it wouldn’t work. Feel free to reach out if you have any other questions and I hope this helps!

Just tried using s3 as the STORAGE_TYPE, deleted the local storage location variable, inputted the s3 variables (you can find them in the Dify docs) for my Cloudflare R2 bucket, deleted the volumes, and deployed it and it worked!

Jack, thoughts on integrating MinIO?

Done! You can either setup an s3 container yourself, re-deploy the template to get a provisioned MinIO bucket, or if you'd like, you can invite me to your project and I can set it up for you if you've already customized your instance and don't wanna restart.

Jack,

I reinstalled Dify, verified that the bucket was created successfully, configured the options in System Model Settings, but when I add a file in KNOWLEDGE it remains in Queuing status

Were you able to use the KNOWLEDGE feature?

I was, would you mind adding me to your project so I could look? Or would you like to talk over discord?

I don't mind… I need your email to add it to my project, right?

I don't mind… I need your email to add it to my project, right?

Yeah, just invite jacklaffin@icloud.com.

done

Can you try uploading a file and sending what the error says? Looks like there’s files in the bucket so that’s odd.

Or you could make me an account inside your Dify workspace so I could try?

I added you to my workspace

Just deployed the template and encountered the same issue, debugging right now and will get back to you with a resolution ASAP.

deleted

It didn't work for me. I sent an invitation to my workspace to your email

Hi Jack,Did you find the cause or solution to this problem?

Hey, not yet unfortunately. Spent a few hours looking into it and validating things but will continue and search. Apologies for the inconvenience.

Right. As I need this feature, I will wait for the solution to install again

I am also facing the same problem. When I upload the knowledge, it stays in the 'queue' and never completes. I have been trying to solve this for days and haven't succeeded. Please let us know when you find a solution.

Hey Jack, I tried to deploy your Dify instance, and even included the S3 bucket keys from Cloudflare r2 (as you mentioned a few messages up), but the knowledegebase items are still stuck in the "queue"I had a chat already, testing multiple things in the Dify Discord here:https://discord.com/channels/1082486657678311454/1249356565501317154Any ideas how to resolve this? or get past this point?

As jack has mentioned a few messages up, he has not been able to get that part of the template working

Hello everydoby, any news? It is a really important help

Hello friends, any solution in view to the queue problem?

I am also still facing the same issue, knowledge is successfully uploaded (to Min.io), but getting stuck in "queuing" status. Using the s3 setup with Min.io as described above. Log attached for reference. Dify variable settings: STORAGE_TYPE=s3, S3_BUCKET_NAME=difyai, S3_ENDPOINT=http://storage.railway.internal:9000, S3_REGION=autoS3_ACCESS_KEY=<properly set>, S3_SECRET_KEY=<properly set>

@jack: would appreciate your support.

Hi Jack. Thanks for creating this template. A lot of us, myself included, have been having trouble running the system, but without success. It's great to have you here. Dify recently updated and added langgenius/dify-sandbox. Could you integrate it into the template to fully utilize Dify's features? Thanks a lot!

Quick update for anyone experiencing issues with the template, they should be resolved and future template deployments should work! If you want to fix your existing deployment, change the image on the Worker service to langgenius/dify-api instead of langgenius/dify-web.

Hi Jack. Thanks for creating this template. A lot of us, myself included, have been having trouble running the system, but without success. It's great to have you here. Dify recently updated and added langgenius/dify-sandbox. Could you integrate it into the template to fully utilize Dify's features? Thanks a lot!

I’ll be sure to look into this and integrate it when I return home next Monday!

Perfect Jack, now it's working perfectly for me. Thank you very much!

Hi guys and tnks Jack for the work, I have tried to deploy the Dify template today (20/08/2024) but it's giving an error saying that something went wrong. No specific info regarding what. Apols but I am new to Railway & Template usage so not sure how to debug more. Tnks!

Hi guys and tnks Jack for the work, I have tried to deploy the Dify template today (20/08/2024) but it's giving an error saying that something went wrong. No specific info regarding what. Apols but I am new to Railway & Template usage so not sure how to debug more. Tnks!

Please ignore my message above - I am leaving my message and the resolution for anybody with the same issue: I discovered that the issue was that I was on a Trial plan. Now with the hobby plan the deployment worked. Tnks and apols again.

Perfect Jack, now it's working perfectly for me. Thank you very much!

Hi again and apols for posting again, but I am having issue with the Sandbox environment - that I see mentioned above - in specific using chatbot chatflow, it is returning the error that I attach in the screenshot. The Worker service is already set to langgenius/dify-api instead of langgenius/dify-web Is it working for you? Tnks for the help.

Same with dpl. With this template, workflow always stop with [Errno 111] when using template or code block. Really want to fix this issue.

hello, friends! I'm with same problem (mago and dpl)... any solutions?

The long-awaited addition of Dify Sandbox is over! It’s finally been added to this template, let me know if you experience any trouble with it.

Hi, any chance to update the template to support the latest release with plugins v1.0.0?

Yeah, they bug in the variable daemon plugin. I cannot configure make all to run.

Which error are you getting with the daemon plugin? I am running a 0.15.3 instance of the template how can I run some commands on the containers in my Railway account to migrate?

I want to start template with version 1.0.0 and got the error below.

I saw there i a new container for that service on docker hub here https://hub.docker.com/r/langgenius/dify-plugin-daemon you might need to add it locally and check if after that things are working. Make sure to get all the env vars set for the container here is an example and let me know if things works https://github.com/langgenius/dify-plugin-daemon/blob/main/.env.example

Can you change the template, I added a new node for dify-daemon-plugin. But config wrong, that makes the node API cannot connect to the node dify-daemon-plugin.

```
SERVER_PORT="5002"

SERVER_KEY="test_api_key"

GIN_MODE="release"

DIFY_INNER_API_KEY="test_api_key"

DIFY_INNER_API_URL="https://${{Api.HOST}}:5001"

PLUGIN_REMOTE_INSTALLING_ENABLED="true"

PLUGIN_REMOTE_INSTALLING_HOST="https://${{HOST}}"

PLUGIN_REMOTE_INSTALLING_PORT="5003"

AWS_ACCESS_KEY="${{Storage.MINIO_ROOT_USER}}"

AWS_SECRET_KEY="${{Storage.MINIO_ROOT_PASSWORD}}"

AWS_REGION="auto"

PLUGIN_STORAGE_TYPE="local"

S3_ACCESS_KEY="${{Storage.MINIO_ROOT_USER}}"

S3_BUCKET_NAME="${{Storage.MINIO_BUCKET}}"

S3_ENDPOINT="${{Storage.MINIO_PRIVATE_ENDPOINT}}"

S3_REGION="auto"

S3_SECRET_KEY="${{Storage.MINIO_ROOT_PASSWORD}}"

SECRET_KEY="83y0rqa04clvu01138v2i7d9wt865o7w"

PLUGIN_INSTALLED_PATH="plugin"

PLUGIN_WORKING_PATH="cwd"

PERSISTENCE_STORAGE_PATH="persistence"

PERSISTENCE_STORAGE_MAX_SIZE="104857600"

PLUGIN_WEBHOOK_ENABLED="true"

ROUTINE_POOL_SIZE="1024"

REDIS_HOST="${{Redis.REDISHOST_PRIVATE}}"

REDIS_PORT="${{Redis.REDISPORT_PRIVATE}}"

REDIS_PASSWORD="${{Redis.REDIS_PASSWORD}}"

DB_USERNAME="${{Postgres.POSTGRES_USER}}"

DB_PASSWORD="${{Postgres.POSTGRES_PASSWORD}}"

DB_HOST="${{Postgres.PGHOST_PRIVATE}}"

DB_PORT="${{Postgres.PGPORT_PRIVATE}}"

DB_DATABASE="${{Postgres.POSTGRES_DB}}"

DIFY_INVOCATION_CONNECTION_IDLE_TIMEOUT="120"

MAX_PLUGIN_PACKAGE_SIZE="52428800"

DIFY_PLUGIN_SERVERLESS_CONNECTOR_URL="https://${{Api.HOST}}:5004"

DIFY_PLUGIN_SERVERLESS_CONNECTOR_API_KEY="test_apikey"

PYTHON_ENV_INIT_TIMEOUT="120"

PPROF_ENABLED="false"

FORCE_VERIFYING_SIGNATURE="true"

```

@jack can you update the template and @datnguyennnx I think you need to create an issue on the dify repo on Github or search in the repo which service is running on port 5004 it seems like another container needs to be provisioned?

Any updates, ser ?

Please do not advertise your template in here, I’ve been working today on getting those updates out. Your template has a lot of default configuration from the .env.example and doesn’t look complete/accurate.

Going to echo what Jack has said here.

Please do not advertise your template on someone else's template forum.

Users have been requesting an update for a long time. You can copy mine and create a new template or update yours fine with me. Only trying to help the community.