Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running on my server #31

Open
ghost opened this issue Apr 1, 2015 · 10 comments
Open

Running on my server #31

ghost opened this issue Apr 1, 2015 · 10 comments

Comments

@ghost
Copy link

ghost commented Apr 1, 2015

Hi

I try install it on Heroku but it not woking, because I use free Heroku, then I try running on my server but not woking

Here error:

Wed Apr 01 2015 14:04:12 GMT+0700 (ICT) – retrying
Wed Apr 01 2015 14:04:14 GMT+0700 (ICT) – fetching
Wed Apr 01 2015 14:04:15 GMT+0700 (ICT) – Error: Hostname/IP doesn't match certificate's altnames
    at SecurePair.<anonymous> (tls.js:1390:23)
    at SecurePair.emit (events.js:92:17)
    at SecurePair.maybeInitFinished (tls.js:980:10)
    at CleartextStream.read [as _read] (tls.js:472:13)
    at CleartextStream.Readable.read (_stream_readable.js:341:10)
    at EncryptedStream.write [as _write] (tls.js:369:25)
    at doWrite (_stream_writable.js:226:10)
    at writeOrBuffer (_stream_writable.js:216:5)
    at EncryptedStream.Writable.write (_stream_writable.js:183:11)
    at write (_stream_readable.js:602:24)
    at flow (_stream_readable.js:611:7)
    at Socket.pipeOnReadable (_stream_readable.js:643:5)
Wed Apr 01 2015 14:04:15 GMT+0700 (ICT) – retrying
Wed Apr 01 2015 14:04:17 GMT+0700 (ICT) – fetching
Wed Apr 01 2015 14:04:18 GMT+0700 (ICT) – Error: Hostname/IP doesn't match certificate's altnames

Anyone help me suggestion a solutions?

@skurfuerst
Copy link

Hey,

I have the same issue but do not know yet what's going on there...

Some pointer would be awesome 💃

Greets, Sebastian

@maccman
Copy link

maccman commented Jun 1, 2015

Also getting this.

@maccman
Copy link

maccman commented Jun 1, 2015

Set the env var NODE_TLS_REJECT_UNAUTHORIZED to 0

@ghost
Copy link
Author

ghost commented Jun 1, 2015

Hi

I have been running again via command

 slackin --port 8080 --interval 60000 "phalconchats"  "tokenslack"

And working

@sigwo
Copy link

sigwo commented Jun 6, 2015

@maccman Where is that set in slackin?

@bryanjacquot
Copy link

I was getting this same error and I fixed it by setting the "your-slack-subdomain". In our case, this was the first portion of grommet.slack.com (grommet).

@zavg
Copy link

zavg commented Jul 1, 2015

Thank you, @maccman

Your suggestion to

Set the env var NODE_TLS_REJECT_UNAUTHORIZED to 0

worked for me!

@jontsai
Copy link

jontsai commented Jul 25, 2015

Thanks @maccman , I fixed this on Heroku by doing

heroku config:set NODE_TLS_REJECT_UNAUTHORIZED=0 --app APP_NAME

@rauchg perhaps this config var should be set in the Heroku app settings so it can truly be one-click deploy?

@rauchg
Copy link
Owner

rauchg commented Jul 26, 2015

@jontsai why do we need this TLS warn in the first place? I wasn't getting this error myself.

@kalashnikovisme
Copy link

@sigwo setting env variables is looking like this.

NODE_TLS_REJECT_UNAUTHORIZED=0 slackin "yourdomain" "yourtoken"

works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants