-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dify startup failed #89
Comments
I removed the |
Do you still get this issue if you update the dify version via If that doesn't fix it you could try:
Then
Check these documents for further information: If this works, let me know and I can start a PR to add this option in the .yml for future updates. |
Hello, Thanks for your help. Unfortunately, it doesn't work for me. I still have the same issue. After looking into deeper, I think the errors start from the Dockerfile at build process, maybe modification at So I tried with FROM pkgxdev/pkgx
WORKDIR /dify2openai
RUN apt-get update && apt-get install -y ca-certificates curl
COPY ./ca-certificates/ /usr/local/share/ca-certificates/
RUN update-ca-certificates
ENV NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt
# Install + warmup
RUN pkgx install node@20 npm
RUN node --version After build the image and run in container, it turn out that with update certificates, I can actually use I don't know what I can try right now, any ideas? @ZacharyKehlGEAppliances Thanks. |
I suspect it might be due to your corporate firewall being very picky about SSL connections it allows and enforcing traffic inspection on all of the allowed ones. Please try updating for v0.2.21, and rebuild the harbor update
harbor build dify See if this |
I am trying to setup Dify, and it was successful with pull
however when i try to start up with
I got error as follows:
I am using corporate network, so I do have a self signed certificate and it is installed to trust store on WSL2 Arch Linux
Thanks for your help!
The text was updated successfully, but these errors were encountered: