Hi,
What response do you get if you enter this on your instance?
which coronium-tools
LMK
it says, /usr/local/bin/coronium-tools
Hi,
Ok, lets recap:
-
You log in with coronium user
-
You issue a sudo coronium-tools wson
2a. You may be prompted for your password
2b. You enter password
-
You should get no result. That means no error. Doesnt mean it worked obviously.
-
You issue a sudo service coronium reload
At that point you should be able to use the WebSocket. You can try issuing the sudo coronium-tools wson again (for good measure).
Success! Thank you!
Hi,
You’ll need a terminal program (Terminal on OSX, Putty on Windows).
You can find your instance IP on the DigitalOcean panel and log in:
ssh coronium@my-droplet-ip
When prompted, enter the password that was used when first installing Coronium.
You shouldn’t need to set up any SSL, the coronium user is already “sudo” enabled.
Hope that helps.
Cheers.
When I ssh with the above, I get a printout in the terminal that starts with:
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-71-generic x86_64)
and includes a bunch of other stuff, then concludes with:
coronium@install:~$
but when I do:
sudo coronium-tools wson
I get:
sudo: unable to resolve host install.coronium.my-instance-name
[sudo] password for coronium:
And I can’t get any further.
Hi,
Are you trying to turn on WebSocket support?
Cheers.
Trying, yes
Hi,
What version of Coronium are you running? Should be in the lower left of the admin UI.
Cheers.
Beta 1.92
I have another app using coronium on digital ocean and when I ssh with the above it all works the way it is supposed to. Can you think of a reason it would fail with this installation? A setting I messed up or something?
Hi,
Is that a newer version?
no, it is also 1.92
Just in case it matters, in the digital ocean dashboard I notice that there are two slightly different versions of ubuntu running. The more current, for the coronium install that I can NOT seem to ssh correctly, is: Ubuntu 14.04.3 x64
While the coronium installation which DOES behave as expected with ssh is running: Ubuntu 14.04 x64
Probably immaterial but just in case.
Hey Chris, so as stated I have two instances. One says it is “unable to resolve host” when I ssh in. The other looks like this:
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-57-generic x86_64)
* Documentation: https://help.ubuntu.com/
System information as of Thu Apr 14 16:48:57 EDT 2016
System load: 0.08 Processes: 84
Usage of /: 27.2% of 19.56GB Users logged in: 0
Memory usage: 58% IP address for eth0: ***
Swap usage: 0%
Graph this data and manage this system at:
https://landscape.canonical.com/
225 packages can be updated.
106 updates are security updates.
coronium@install:~$ sudo coronium-tools wson
[sudo] password for coronium:
coronium@install:~$
But after running “sudo coronium-tools wson” and trying the 01_simple example from the docs, I get nothing printed to the screen, and this error in the logs:
2016/04/14 16:50:22 [error] 8267#0: *10735143 open() “/usr/local/openresty/nginx/html/ws” failed (2: No such file or directory), client: 134.69.86.23, server: , request: “GET /ws HTTP/1.1”, host: “***”
Hi,
Are both of these instances 1.92? Also, Coronium supports any Ubuntu 14.04.x revision.
Also you can update that box with:
sudo apt-get update -y; sudo apt-get upgrade -y
I’ll be looking into this, but it’s on a list of other things as well. I’ll try to look over the weekend.
Cheers.
Both 1.92. Thanks for fitting it in when you can.
Just to further update you I spun up a brand new digital ocean droplet, installed a fresh instance of coronium, and was not able to activate web sockets.
You trying to add https, I just use cloud flare (which is free) and does not require terminal if you already have coronium installed.
Hi,
My apologies that this keeps getting pushed back. Looking into it now. You are talking about WebSockets though, correct?
Cheers.