You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and this bug is not already filed.
My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.
Describe the bug
Due to this documented issue with tiktoken, running graphrag in a disconnected or locked down scenario (where it can't reach the open internet) causes 443 SSL errors to fail.
I wanted to document for the community that this is a known issue in a dependent library and that workarounds or fixes could be proposed. Or the dev team could implement a permanent solution.
Steps to reproduce
Run graphrag in a network that does not have open internet access.
Deploy Azure Open AI
Deploy a vnet that disallows internet access.
Deploy a dev Vm in that vnet.
Use AOAI with graphrag on that dev VM
Expected Behavior
No response
GraphRAG Config Used
# Paste your config here
Logs and screenshots
No response
Additional Information
GraphRAG Version:
Operating System:
Python Version:
Related Issues:
The text was updated successfully, but these errors were encountered:
Do you need to file an issue?
Describe the bug
Due to this documented issue with tiktoken, running graphrag in a disconnected or locked down scenario (where it can't reach the open internet) causes 443 SSL errors to fail.
I wanted to document for the community that this is a known issue in a dependent library and that workarounds or fixes could be proposed. Or the dev team could implement a permanent solution.
Steps to reproduce
Run graphrag in a network that does not have open internet access.
Expected Behavior
No response
GraphRAG Config Used
# Paste your config here
Logs and screenshots
No response
Additional Information
The text was updated successfully, but these errors were encountered: