opsvr202
opsvr202
This issue was first discovered in v0.6.8. I upgraded to v0.6.9, but the bug still exists。   ![Uploading bfffe5fca9f61a5eac5d3f610554632.jpg…]()
> > 您在使用 Dify v1.0.0 时遇到的问题`ConnectionError`是一个已知问题，即由于与“openapublic.blob.core.windows.net”相关的问题导致正常对话和文档嵌入失败。此错误通常发生在系统尝试在离线或受限网络环境中访问此端点时。相同的设置在版本 v0.15.3 上正常运行，这表明该问题特定于 v1.0.0 [[1]](https://github.com/langgenius/dify/issues/14485)中引入的更改。 > > 为了解决这个问题，您可以考虑恢复到最新的稳定版本 (v0.15.3)，直到 v1.0.0 正式发布并解决这些问题。此外，请确保您的网络设置允许访问所需的外部资源，或者在必要时考虑配置代理。 > > _要继续与[Dosu](https://dosu.dev)交谈，请提及[@dosu](https://github.com/dosu)。_ > > 帮助 Dosu 学习！提供反馈：[很好的回应](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=great_response)|[不相关的答案](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=irrelevant_answer)|[不正确的来源](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=incorrect_sources)|[太冗长](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=too_verbose)|[幻觉](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=hallucination)|[错误报告](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=bug_report)|[其他](https://app.dosu.dev/response-feedback/eca4dd79-f1a9-4eb4-8687-305a0bd2375a?feedback_type=other) > > 但是在0.15.3版本中，旧版本的chrome会报错说toReversed不是函数，该如何解决？ This is also...
> [参考：](https://stackoverflow.com/questions/76106366/how-to-use-tiktoken-in-offline-mode-computer) https://stackoverflow.com/questions/76106366/how-to-use-tiktoken-in-offline-mode-computer 下载 vocab.bpe encoder.json 放到缓存 > > ``` > mkdir tiktoken > cd tiktoken > wget https://openaipublic.blob.core.windows.net/gpt-2/encodings/main/vocab.bpe > cp vocab.bpe 6d1cbeee0f20b3d9449abfede4726ed8212e3aee > wget https://openaipublic.blob.core.windows.net/gpt-2/encodings/main/encoder.json > cp encoder.json 6c7ea1a7e38e3a7f062df639a5b80947f075ffe6...
> Can you paste the error details in text? Sorry, the data is in the intranet and cannot be accessed in the external network environment
> The image you took is a little bit vague, can you take a new picture again? Okay, I'll take another picture：  