Skip to content
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

openspg configuration issue #515

Open
suibianha opened this issue Mar 6, 2025 · 0 comments
Open

openspg configuration issue #515

suibianha opened this issue Mar 6, 2025 · 0 comments

Comments

@suibianha
Copy link

suibianha commented Mar 6, 2025

Strictly following the configuration steps listed in the latest version of user manual, and proceeding to the step on section 3.1.1, the following issue occurred when doing global configuration:

Image

From within the release-openspg-server container, there is no issue connecting to the other container release-openspg-neo4j via telnet with IP.

Tried changing the URI field in several different formats, including changing the prefix from "neo4j" to "bolt" and using the internal IP of release-openspg-neo4j to replace the container name "release-openspg-neo4j", none of them work and all resulted in the same error.

Neither of the related docker containers release-openspg-server and release-openspg-neo4j has any related error information appearing in the log, in fact when the timeout error happened, no new log was printed in either of the containers AT ALL.

Can somebody help with identifying this issue and/or provide any temporary methods to bypass this step and to proceed with creating the project please? Thank you.

P.S.

Connectivity issue also occurred when trying developer mode (not sure with similar reason or not), while proceeding to creating project with knext using the example_config.yaml, the following error occurred:

Error: invalid llm config: {'api_key': '<my_api_key>', 'base_url': 'https://api.deepseek.com', 'model': 'deepseek-chat', 'type': 'maas'}, for details: Connection error.

The API key is used and tested separately and is definitely valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant