C
C
Const V2015-10-16 15:06:29
Apache HTTP Server
Const V, 2015-10-16 15:06:29

Why can't I connect to cloud9 stopped on a DigitalOcean VPS?

I tried to use the cloud IDE cloud9 c9.io . I liked it, but the free account has limitations and I decided to try installing this IDE on the simplest VPS. The first googled solution was to install a Docker container with the environment already set up, but there were difficulties opening FTP through the environment options and the working files themselves were hidden deep in the container. That is - everything works fine, but some inferiority of the solution is annoying.
I decided to try to install this development environment in the "official" way, from their github: https://github.com/c9/core
Created a new droplet with pure Ubuntu 14.04 and started installing it one by one required packages and software:
Apache: https://www.digitalocean.com/community/tutorials/l...
Git:https://www.digitalocean.com/community/tutorials/g...
Node: https://www.digitalocean.com/community/tutorials/n...
Ruby: https://www.digitalocean.com/ community/tutorials/h...
When everything worked, I installed cloud9 according to the instructions from the github. At the last step, the installer writes that everything was successful:

Success!
run 'node server.js -p 8080 -a :' to launch Cloud9

After executing the command "node server.js -p 8080 -a :" or just "node server.js" the server starts with the following message:
Starting standalone
Connect server listening at http://127.0.0.1:8181
CDN: version standalone initialized /root/c9sdk/build
Started '/root/c9sdk/configs/standalone' with config 'standalone'!

I do not understand, does this mean that there are no errors and everything works? Or are there problems? Because it's impossible to open ide in the browser, I ran it with different port numbers - the result is the same, "The page cannot be displayed". Apache is working fine, but I can't connect to cloud9... What did I do wrong?
Test vps in DO: 95.85.2.93 , root password: 1234

Answer the question

In order to leave comments, you need to log in

1 answer(s)
C
Chvalov, 2015-10-16
@Chvalov

First, remove and change the password from the root, it's stupid to distribute passwords to everyone
. I really didn’t work with this case, but it seems to me that it just works, but in the LAN 127.0
. also on the internet

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question