Closed The-Stuke closed 5 months ago
Introspection is disable by default for security purpose. You can activate it in config with force_disabled_introspection
```
"graphql": { "armor_enabled": false, "batching_protection": { "mutation_default": 1, "query_default": 2, "query_subtypes": 4 }, "playground": { "enabled": true, "force_disabled_introspection": true } },
Tracing and apollo federation are not supported.
Thank you I was not aware of that configuration. I found the reference in the documentation for APP__GRAPHQL_PLAYGROUND__FORCE_DISABLED_INTROSPECTION. I have tried this variable on both false and true in my config. In both cases I am receiving the same as I shared above on version 6.1.3. Docs and Schema constantly load and the "Server cannot be reached" error is still present.
As for expected output I spun up a quick instance of 6.0.7 as I knew it loaded the other day. It looks like it was working back in this version. I left out the APP__GRAPHQL_PLAYGROUND__FORCE_DISABLED_INTROSPECTION in my config for this example. Below are what I was hoping to see in the latest version.
I spun up a few instances to see what version of OpenCTI this quit working in. The last known working I can reproduce is 6.0.10. As soon as I went to 6.1.0 it goes into this constant loading state and Server cannot be reached error message.
https://github.com/OpenCTI-Platform/opencti/issues/6992
This closed issue looks to be the same. Both false and true produces the same results.
@The-Stuke,
Typo in the doc: APP__GRAPHQL__PLAYGROUND__FORCE_DISABLED_INTROSPECTION=true
instead of APP__GRAPHQL_PLAYGROUND__FORCE_DISABLED_INTROSPECTION=true
.
I've fixed the doc.
Description
When trying to use the graphql playground there are issues when trying to load any Schema, Docs, Tracing, or Query Plan. They either constantly load or gives errors. I am able to query data though by inputing a query and pressing the play button. I am just not able to view the Docs, Schema, Tracing, or Query Plan. I tried this on a fresh install of OpenCTI as well.
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
Schema, Docs, Tracing, or Query Plan to populate. Along with server cannot be reached message to not be there.
Actual Output
Schema, Docs, Tracing, or Query Plan is not loading any data or giving other errors.
Additional information
Constant 500 error can be seen on the web browser network console when looking at this
Docker compose
I didn't see any errors present in INFO level logging, but turning it to debugging I saw some errors like this
Screenshots (optional)
Able to pull data with a query, but shows Server cannot be reached.
Errors of data not loading