dokku: Node JS app not working

Description of problem:

I’ve installed Dokku using the one click app in Digital Ocean, in Ubuntu 16.04. I’ve tried running the Node JS sample of Heroku and it builds just fine and it outputs a url (Which is my server ip with the port). The problem is that when I put this url on my browser, it tries to load it for a long time but it does nothing. I think is something with related with ports, maybe?

(I’ll try to complete most of the things below)

Output of the following commands

• uname -a: Linux XsomenameX-dokku 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

• free -m:

              total        used        free      shared  buff/cache   available
Mem:            488          77          65           5         345         371
Swap:             0           0           0

• docker version:

Client: Version: 1.12.4 API version: 1.24 Go version: go1.6.4 Git commit: 1564f02 Built: Tue Dec 13 00:08:34 2016 OS/Arch: linux/amd64

Server: Version: 1.12.4 API version: 1.24 Go version: go1.6.4 Git commit: 1564f02 Built: Tue Dec 13 00:08:34 2016 OS/Arch: linux/amd64

• docker -D info:

Containers: 8 –> THIS LOOKS ODD, I ONLY HAVE ONE APP Running: 1 Paused: 0 Stopped: 7 Images: 17 Server Version: 1.12.4 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 36 Dirperm1 Supported: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: host bridge overlay null Swarm: inactive Runtimes: runc Default Runtime: runc Security Options: apparmor seccomp Kernel Version: 4.4.0-53-generic Operating System: Ubuntu 16.04.1 LTS OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 488.5 MiB Name: XsomenameX-dokku ID: LJ2H:FYCT:5DKP:AMOL:R6IL:T5F6:G2GN:OSXH:EASL:IXMS:JPQB:6J2A Docker Root Dir: /var/lib/docker Debug Mode (client): true Debug Mode (server): false Registry: https://index.docker.io/v1/ Insecure Registries: 127.0.0.0/8

• sigil -v:

0.4.0

• docker run -ti gliderlabs/herokuish:latest herokuish version:

herokuish: 0.3.19 buildpacks: heroku-buildpack-multi v1.0.0 heroku-buildpack-ruby v146 heroku-buildpack-nodejs v91 heroku-buildpack-clojure v75 heroku-buildpack-python v82 heroku-buildpack-java v46 heroku-buildpack-gradle v18 heroku-buildpack-grails v21 heroku-buildpack-scala v72 heroku-buildpack-play v26 heroku-buildpack-php v110 heroku-buildpack-go v44 heroku-buildpack-erlang fa17af9 buildpack-nginx v6 emberjs.tgz latest

• dokku version:

0.7.2

• dokku plugin:

plugn: 0.2.2 00_dokku-standard 0.7.2 enabled dokku core standard plugin 20_events 0.7.2 enabled dokku core events logging plugin apps 0.7.2 enabled dokku core apps plugin build-env 0.7.2 enabled dokku core build-env plugin certs 0.7.2 enabled dokku core certificate management plugin checks 0.7.2 enabled dokku core checks plugin common 0.7.2 enabled dokku core common plugin config 0.7.2 enabled dokku core config plugin docker-options 0.7.2 enabled dokku core docker-options plugin domains 0.7.2 enabled dokku core domains plugin enter 0.7.2 enabled dokku core enter plugin git 0.7.2 enabled dokku core git plugin logs 0.7.2 enabled dokku core logs plugin named-containers 0.7.2 enabled dokku core named containers plugin nginx-vhosts 0.7.2 enabled dokku core nginx-vhosts plugin plugin 0.7.2 enabled dokku core plugin plugin proxy 0.7.2 enabled dokku core proxy plugin ps 0.7.2 enabled dokku core ps plugin repo 0.7.2 enabled dokku core repo plugin shell 0.7.2 enabled dokku core shell plugin ssh-keys 0.7.2 enabled dokku core ssh-keys plugin storage 0.7.2 enabled dokku core storage plugin tags 0.7.2 enabled dokku core tags plugin tar 0.7.2 enabled dokku core tar plugin

• docker inspect CONTAINER_ID (if applicable): (BEWARE: docker inspect will print environment variables for some commands, be sure you’re not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
• cat /home/dokku/<app>/nginx.conf (if applicable):
• Link to the exact repository being deployed (if possible/applicable):
• If a deploy is failing or behaving unexpectedly:
  • Application name
  • The type of application being deployed (node, php, python, ruby, etc.)
  • If using buildpacks, which custom buildpacks are in use
  • If using a Dockerfile, the contents of that file
  • If it exists, the contents of your Procfile.
• Output of failing Dokku commands after running dokku trace on (BEWARE: trace on will print environment variables for some commands, be sure you’re not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):

Environment details (AWS, VirtualBox, physical, etc.): DigitalOcean

How was Dokku installed?: One click app

How reproducible:

Steps to Reproduce (After creating a dokku app):

1. Clone this repository https://github.com/heroku/node-js-sample
2. Push it to dokku
3. Try to use the url in the output

Actual Results:

Not working

Expected Results:

See a “hello world”

Additional info:

• nginx -t:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful