Cannot get access by link to the node.js server running inside the dokku
I have a node.js server running inside the dokku on port 8080 but I cannot get access to it by opening the link http://my-digital-ocean-ip:8080. I checked the logs of the application, the server was successfully started on port 8080: here is a screenshot of logs.
For running the server I'm using graphql-yoga but I think it is more Digital Ocean problem, maybe something about configs or hosts because if I run the application on my local machine, it will be successfully opened on http://localhost:4000 (4000 is default port).
Also, I have another one dokku application running on the same Digital Ocean droplet on the port 4646 and it works perfectly but it is not a node.js application, it is prisma service. I tried to run only one of these dokku applications but it didn't effect anyhow.
Also, I tried to change 8080 port to 4000, 80 and it didn't help either.
Here is the code of my index.js:
require('dotenv').config();
const GraphQLServer = require('graphql-yoga');
const prisma = require('./generated');
const resolvers = require('./resolvers');
const server = new GraphQLServer(
typeDefs: 'src/schema.graphql',
resolvers: resolvers,
context:
prisma: prisma,
,
resolverValidationOptions:
requireResolversForResolveType: false,
,
);
server.start(( port ) => console.log(`GraphQL server is running on the port $port`));
Here is the code of the Dockerfile:
FROM node:10.13.0
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 8080
CMD [ "npm", "start" ]
Here is my repo - https://github.com/SilencerWeb/follow-api-server/tree/development
node.js digital-ocean dokku
add a comment |
I have a node.js server running inside the dokku on port 8080 but I cannot get access to it by opening the link http://my-digital-ocean-ip:8080. I checked the logs of the application, the server was successfully started on port 8080: here is a screenshot of logs.
For running the server I'm using graphql-yoga but I think it is more Digital Ocean problem, maybe something about configs or hosts because if I run the application on my local machine, it will be successfully opened on http://localhost:4000 (4000 is default port).
Also, I have another one dokku application running on the same Digital Ocean droplet on the port 4646 and it works perfectly but it is not a node.js application, it is prisma service. I tried to run only one of these dokku applications but it didn't effect anyhow.
Also, I tried to change 8080 port to 4000, 80 and it didn't help either.
Here is the code of my index.js:
require('dotenv').config();
const GraphQLServer = require('graphql-yoga');
const prisma = require('./generated');
const resolvers = require('./resolvers');
const server = new GraphQLServer(
typeDefs: 'src/schema.graphql',
resolvers: resolvers,
context:
prisma: prisma,
,
resolverValidationOptions:
requireResolversForResolveType: false,
,
);
server.start(( port ) => console.log(`GraphQL server is running on the port $port`));
Here is the code of the Dockerfile:
FROM node:10.13.0
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 8080
CMD [ "npm", "start" ]
Here is my repo - https://github.com/SilencerWeb/follow-api-server/tree/development
node.js digital-ocean dokku
add a comment |
I have a node.js server running inside the dokku on port 8080 but I cannot get access to it by opening the link http://my-digital-ocean-ip:8080. I checked the logs of the application, the server was successfully started on port 8080: here is a screenshot of logs.
For running the server I'm using graphql-yoga but I think it is more Digital Ocean problem, maybe something about configs or hosts because if I run the application on my local machine, it will be successfully opened on http://localhost:4000 (4000 is default port).
Also, I have another one dokku application running on the same Digital Ocean droplet on the port 4646 and it works perfectly but it is not a node.js application, it is prisma service. I tried to run only one of these dokku applications but it didn't effect anyhow.
Also, I tried to change 8080 port to 4000, 80 and it didn't help either.
Here is the code of my index.js:
require('dotenv').config();
const GraphQLServer = require('graphql-yoga');
const prisma = require('./generated');
const resolvers = require('./resolvers');
const server = new GraphQLServer(
typeDefs: 'src/schema.graphql',
resolvers: resolvers,
context:
prisma: prisma,
,
resolverValidationOptions:
requireResolversForResolveType: false,
,
);
server.start(( port ) => console.log(`GraphQL server is running on the port $port`));
Here is the code of the Dockerfile:
FROM node:10.13.0
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 8080
CMD [ "npm", "start" ]
Here is my repo - https://github.com/SilencerWeb/follow-api-server/tree/development
node.js digital-ocean dokku
I have a node.js server running inside the dokku on port 8080 but I cannot get access to it by opening the link http://my-digital-ocean-ip:8080. I checked the logs of the application, the server was successfully started on port 8080: here is a screenshot of logs.
For running the server I'm using graphql-yoga but I think it is more Digital Ocean problem, maybe something about configs or hosts because if I run the application on my local machine, it will be successfully opened on http://localhost:4000 (4000 is default port).
Also, I have another one dokku application running on the same Digital Ocean droplet on the port 4646 and it works perfectly but it is not a node.js application, it is prisma service. I tried to run only one of these dokku applications but it didn't effect anyhow.
Also, I tried to change 8080 port to 4000, 80 and it didn't help either.
Here is the code of my index.js:
require('dotenv').config();
const GraphQLServer = require('graphql-yoga');
const prisma = require('./generated');
const resolvers = require('./resolvers');
const server = new GraphQLServer(
typeDefs: 'src/schema.graphql',
resolvers: resolvers,
context:
prisma: prisma,
,
resolverValidationOptions:
requireResolversForResolveType: false,
,
);
server.start(( port ) => console.log(`GraphQL server is running on the port $port`));
Here is the code of the Dockerfile:
FROM node:10.13.0
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 8080
CMD [ "npm", "start" ]
Here is my repo - https://github.com/SilencerWeb/follow-api-server/tree/development
node.js digital-ocean dokku
node.js digital-ocean dokku
edited Nov 13 '18 at 10:31
Andrew Koten
asked Nov 13 '18 at 10:22
Andrew KotenAndrew Koten
12
12
add a comment |
add a comment |
0
active
oldest
votes
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%2f53278812%2fcannot-get-access-by-link-to-the-node-js-server-running-inside-the-dokku%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53278812%2fcannot-get-access-by-link-to-the-node-js-server-running-inside-the-dokku%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