Error when running in cli #2

New Issue

Ghost · 2018-10-13T17:49:10Z

Ghost commented

2018-10-13 17:49:10 +00:00

Node v10.7.0

Cannot run sclient

.nvm/versions/node/v10.7.0/bin/sclient: 1: .nvm/versions/node/v10.7.0/bin/sclient: use strict: not found

.nvm/versions/node/v10.7.0/bin/sclient: 3: .nvm/versions/node/v10.7.0/bin/sclient: Syntax error: "(" unexpected

Node v10.7.0 Cannot run sclient ``` .nvm/versions/node/v10.7.0/bin/sclient: 1: .nvm/versions/node/v10.7.0/bin/sclient: use strict: not found .nvm/versions/node/v10.7.0/bin/sclient: 3: .nvm/versions/node/v10.7.0/bin/sclient: Syntax error: "(" unexpected ```

coolaj86 commented

2018-10-14 01:20:44 +00:00

Doh! It’s missing the #!/usr/bin/env node up at the top.

I’m AFK tonight, but you can also download and use the standalone Go version:

https://telebit.cloud/sclient

The Go version is slightly behind the node version I’m terms of some of the shortcut methods, but the core functionality is identical.

Or you could it the file npm installed and add the missing bash header described above.

Doh! It’s missing the `#!/usr/bin/env node` up at the top. I’m AFK tonight, but you can also download and use the standalone Go version: https://telebit.cloud/sclient The Go version is slightly behind the node version I’m terms of some of the shortcut methods, but the core functionality is identical. Or you could it the file npm installed and add the missing bash header described above.

coolaj86 commented

2018-10-14 01:22:37 +00:00

I actually don’t know how nvm works, but if it’s not doing anything too fancy this is the file that needs the bash header:

.nvm/versions/node/v10.7.0/bin/sclient

I’ll fix it tomorrow.

I actually don’t know how nvm works, but if it’s not doing anything too fancy this is the file that needs the bash header: `.nvm/versions/node/v10.7.0/bin/sclient` I’ll fix it tomorrow.

coolaj86 commented

2018-10-15 21:43:25 +00:00

Published v1.4.3 with the bash header fix. Please test and close.

coolaj86 self-assigned this 2018-10-15 21:44:02 +00:00

Ghost commented

2018-10-16 14:38:53 +00:00

It is working now...

Ghost closed this issue

2018-10-16 14:38:53 +00:00

coolaj86 commented

2018-10-17 05:06:12 +00:00

Awesome. If you can spare another minute, I'm curious to know two things:

How did you find out about sclient?
What are you using it for?

Awesome. If you can spare another minute, I'm curious to know two things: 1. How did you find out about sclient? 2. What are you using it for?

Ghost commented

2018-10-17 12:15:11 +00:00

I was searching for vpn solution and heard about telebit in Javascript Jabber Podcast. Through that ended up in this project.

I am using telebit for connecting my Media server via raspberrypi.

Currently i am just hacking around and trying to run telebit in heroku.

I was searching for vpn solution and heard about telebit in Javascript Jabber Podcast. Through that ended up in this project. I am using telebit for connecting my Media server via raspberrypi. Currently i am just hacking around and trying to run telebit in heroku.

coolaj86 commented

2018-10-17 20:43:29 +00:00

I don't think you'll be able to run the telebit remote on Heroku due to how Heroku force-closes stale connections (and deletes files, so the certs would be lost, regenerated, and rate limited - which could affect other users if you're using the telebit.io domains, so please don't do that).

I don't think you'll be able to run the telebit relay on Heroku without paying a ton of money because of the multiple domains and wildcard routing.

I'd recommend trying to get it running on Digital Ocean instead, which is a better fit for an always-on, always-connected type of application.

Are you trying to run the remote or the relay?

I don't think you'll be able to run the telebit remote on Heroku due to how Heroku force-closes stale connections (and deletes files, so the certs would be lost, regenerated, and rate limited - which could affect other users if you're using the telebit.io domains, so please don't do that). I don't think you'll be able to run the telebit relay on Heroku without paying a ton of money because of the multiple domains and wildcard routing. I'd recommend trying to get it running on Digital Ocean instead, which is a better fit for an always-on, always-connected type of application. Are you trying to run the remote or the relay?

Ghost commented

2018-10-18 18:33:02 +00:00

I was trying relay. I will try Digital Ocean instead

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coolaj86/sclient.js#2