Graphql Yoga Playground with Lambda - “Server cannot be reached”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm in the process of setting a graphql endpoint with servlerless/ lambda and am receiving an error when trying to connect to the graphql playground that comes with graphql-yoga. When I go to my route that has the playground (/playground) it launches the playground interface however it just says:
Server cannot be reached
In the top right of the playground. It's worth noting i'm using the makeRemoteExecutableSchema utility to proxy to another graphql endpoint (which is my CMS called Prismic). I don't believe this is the issue as I have successfully connected to it with the playground when testing on a normal express server.
Here is the code in my handler.js
'use strict';
const { makeRemoteExecutableSchema } = require('graphql-tools');
const { PrismicLink } = require("apollo-link-prismic");
const { introspectSchema } = require('graphql-tools');
const { ACCESS_TOKEN, CMS_URL } = process.env;
const { GraphQLServerLambda } = require('graphql-yoga')
const lambda = async () => {
const link = PrismicLink({
uri: CMS_URL,
accessToken: ACCESS_TOKEN
});
const schema = await introspectSchema(link);
const executableSchema = makeRemoteExecutableSchema({
schema,
link,
});
return new GraphQLServerLambda({
schema: executableSchema,
context: req => ({ ...req })
});
}
exports.playground = async (event, context, callback) => {
context.callbackWaitsForEmptyEventLoop = false;
const graphQl = await lambda();
return graphQl.playgroundHandler(event, context, callback);
};
I have followed this guide for getting it running up till here and am fairly sure i've followed similar steps for what applies to what i'm trying to do but can't seem to figure out where i've gone wrong.
Thanks,
javascript node.js aws-lambda graphql
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
add a comment |
I'm in the process of setting a graphql endpoint with servlerless/ lambda and am receiving an error when trying to connect to the graphql playground that comes with graphql-yoga. When I go to my route that has the playground (/playground) it launches the playground interface however it just says:
Server cannot be reached
In the top right of the playground. It's worth noting i'm using the makeRemoteExecutableSchema utility to proxy to another graphql endpoint (which is my CMS called Prismic). I don't believe this is the issue as I have successfully connected to it with the playground when testing on a normal express server.
Here is the code in my handler.js
'use strict';
const { makeRemoteExecutableSchema } = require('graphql-tools');
const { PrismicLink } = require("apollo-link-prismic");
const { introspectSchema } = require('graphql-tools');
const { ACCESS_TOKEN, CMS_URL } = process.env;
const { GraphQLServerLambda } = require('graphql-yoga')
const lambda = async () => {
const link = PrismicLink({
uri: CMS_URL,
accessToken: ACCESS_TOKEN
});
const schema = await introspectSchema(link);
const executableSchema = makeRemoteExecutableSchema({
schema,
link,
});
return new GraphQLServerLambda({
schema: executableSchema,
context: req => ({ ...req })
});
}
exports.playground = async (event, context, callback) => {
context.callbackWaitsForEmptyEventLoop = false;
const graphQl = await lambda();
return graphQl.playgroundHandler(event, context, callback);
};
I have followed this guide for getting it running up till here and am fairly sure i've followed similar steps for what applies to what i'm trying to do but can't seem to figure out where i've gone wrong.
Thanks,
javascript node.js aws-lambda graphql
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41
add a comment |
I'm in the process of setting a graphql endpoint with servlerless/ lambda and am receiving an error when trying to connect to the graphql playground that comes with graphql-yoga. When I go to my route that has the playground (/playground) it launches the playground interface however it just says:
Server cannot be reached
In the top right of the playground. It's worth noting i'm using the makeRemoteExecutableSchema utility to proxy to another graphql endpoint (which is my CMS called Prismic). I don't believe this is the issue as I have successfully connected to it with the playground when testing on a normal express server.
Here is the code in my handler.js
'use strict';
const { makeRemoteExecutableSchema } = require('graphql-tools');
const { PrismicLink } = require("apollo-link-prismic");
const { introspectSchema } = require('graphql-tools');
const { ACCESS_TOKEN, CMS_URL } = process.env;
const { GraphQLServerLambda } = require('graphql-yoga')
const lambda = async () => {
const link = PrismicLink({
uri: CMS_URL,
accessToken: ACCESS_TOKEN
});
const schema = await introspectSchema(link);
const executableSchema = makeRemoteExecutableSchema({
schema,
link,
});
return new GraphQLServerLambda({
schema: executableSchema,
context: req => ({ ...req })
});
}
exports.playground = async (event, context, callback) => {
context.callbackWaitsForEmptyEventLoop = false;
const graphQl = await lambda();
return graphQl.playgroundHandler(event, context, callback);
};
I have followed this guide for getting it running up till here and am fairly sure i've followed similar steps for what applies to what i'm trying to do but can't seem to figure out where i've gone wrong.
Thanks,
javascript node.js aws-lambda graphql
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
I'm in the process of setting a graphql endpoint with servlerless/ lambda and am receiving an error when trying to connect to the graphql playground that comes with graphql-yoga. When I go to my route that has the playground (/playground) it launches the playground interface however it just says:
Server cannot be reached
In the top right of the playground. It's worth noting i'm using the makeRemoteExecutableSchema utility to proxy to another graphql endpoint (which is my CMS called Prismic). I don't believe this is the issue as I have successfully connected to it with the playground when testing on a normal express server.
Here is the code in my handler.js
'use strict';
const { makeRemoteExecutableSchema } = require('graphql-tools');
const { PrismicLink } = require("apollo-link-prismic");
const { introspectSchema } = require('graphql-tools');
const { ACCESS_TOKEN, CMS_URL } = process.env;
const { GraphQLServerLambda } = require('graphql-yoga')
const lambda = async () => {
const link = PrismicLink({
uri: CMS_URL,
accessToken: ACCESS_TOKEN
});
const schema = await introspectSchema(link);
const executableSchema = makeRemoteExecutableSchema({
schema,
link,
});
return new GraphQLServerLambda({
schema: executableSchema,
context: req => ({ ...req })
});
}
exports.playground = async (event, context, callback) => {
context.callbackWaitsForEmptyEventLoop = false;
const graphQl = await lambda();
return graphQl.playgroundHandler(event, context, callback);
};
I have followed this guide for getting it running up till here and am fairly sure i've followed similar steps for what applies to what i'm trying to do but can't seem to figure out where i've gone wrong.
Thanks,
javascript node.js aws-lambda graphql
javascript node.js aws-lambda graphql
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
edited Jan 4 at 12:36
John Rotenstein
79.1k790140
79.1k790140
asked Jan 4 at 10:28
red house 87red house 87
2231030
asked Jan 4 at 10:28
red house 87red house 87
2231030
asked Jan 4 at 10:28
red house 87red house 87
2231030
2231030
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41
add a comment |
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41
add a comment |
1 Answer
1
active
oldest
votes
Could you take a look at what version of the graphql-yoga package you are using?
I had a similar problem using the Apollo server in combination with Kentico Cloud Headless CMS and I found this issue:
- https://github.com/prisma/graphql-yoga/issues/267
answered Jan 15 at 16:46
Simply007Simply007
146110
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54037128%2fgraphql-yoga-playground-with-lambda-server-cannot-be-reached%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Could you take a look at what version of the graphql-yoga package you are using?
I had a similar problem using the Apollo server in combination with Kentico Cloud Headless CMS and I found this issue:
- https://github.com/prisma/graphql-yoga/issues/267
answered Jan 15 at 16:46
Simply007Simply007
146110
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
add a comment |
Could you take a look at what version of the graphql-yoga package you are using?
I had a similar problem using the Apollo server in combination with Kentico Cloud Headless CMS and I found this issue:
- https://github.com/prisma/graphql-yoga/issues/267
answered Jan 15 at 16:46
Simply007Simply007
146110
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
add a comment |
Could you take a look at what version of the graphql-yoga package you are using?
I had a similar problem using the Apollo server in combination with Kentico Cloud Headless CMS and I found this issue:
- https://github.com/prisma/graphql-yoga/issues/267
answered Jan 15 at 16:46
Simply007Simply007
146110
Could you take a look at what version of the graphql-yoga package you are using?
I had a similar problem using the Apollo server in combination with Kentico Cloud Headless CMS and I found this issue:
- https://github.com/prisma/graphql-yoga/issues/267
answered Jan 15 at 16:46
Simply007Simply007
146110
edited Jan 16 at 5:47
answered Jan 15 at 16:46
Simply007Simply007
146110
answered Jan 15 at 16:46
Simply007Simply007
146110
answered Jan 15 at 16:46
Simply007Simply007
146110
146110
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
add a comment |
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
I have also faced some problems that on the production environment is playground turned off by default and you need to programmatically turn it on when creating the endpoint. And also allow introspection to allow playground to load the schema definition.
– Simply007
Jan 16 at 8:58
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54037128%2fgraphql-yoga-playground-with-lambda-server-cannot-be-reached%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should check the network tab in Chrome Dev Tools to see the HTTP request it fires to your graphql endpoint. Hopefully, it will tell you more about the error and if you post it here, someone might be able to help.
– dashmug
Jan 11 at 13:54
The tutorial you are using does not talk about permissions. Have you configured permissions for you lambda to allow network requests?
– itaintme
Jan 11 at 14:41