Node.js and express and production ssl certificate -

-

i'm having problems implement ssl certificate using node.js.

everything works fine localhost, move ubuntu server, multiple problems occur.

i've minimized following code.
certificates (.crt) , keys (.key) in certificates directory, names localhost.key or examplesslserver.crt. i'm using rapidssl certificate , told needed include intermediate certificate.

function serverssl(host,port,intermediate) {     var https   = require('https');     var fs      = require('fs');     var express = require('express');     var app = express();     var httpsoptions = {         key:  fs.readfilesync('certificates/' + host + '.key'),         cert: fs.readfilesync('certificates/' + host + '.crt')     };     if (intermediate) {         httpsoptions.ca = [fs.readfilesync('certificates/' + intermediate + '.crt')];     }     var server = https.createserver(httpsoptions, app).listen({         port:  port,         host: host     }, initserver);      function initserver() {         var host = server.address().address,             port = server.address().port;         console.log(           'example app listening @ https://%s:%s', host, port);     }      app.get('/hello', function (req, res) {         var msg = 'hello ssl';         console.log(msg);         res.send(msg);     }); }

i've tried 2 different calls either

  1. serverssl('localhost',8445);
  2. serverssl('examplesslserver.com',8445,'intermediate')

localhost works fine, when use server, following stack error:

error: listen eaddrnotavail 52.xxx.xxx.xxx:8445     @ object.exports._errnoexception (util.js:873:11)     @ exports._exceptionwithhostport (util.js:896:20)     @ server._listen2 (net.js:1237:19)     @ listen (net.js:1286:10)     @ net.js:1395:9     @ getaddrinforeqwrap.asynccallback [as callback] (dns.js:64:16)     @ getaddrinforeqwrap.onlookup [as oncomplete] (dns.js:83:10)

if take out host argument, doesn't fail, doesn't respond. changed code slight use http vs. https , things seem work fine. also, i've tried many different ports, same problem occurs.

their might problem ssl certificate, have no easy way debug it. i'd happy try tool.

in case, appreciated.


Comments

Post a Comment

Popular posts from this blog

sql - invalid in the select list because it is not contained in either an aggregate function -

-
i can't figure out rewrite sql statement avoid error below msg 8120, level 16, state 1, line 26 column 'staffmember.staffmemberid' invalid in select list because not contained in either aggregate function or group clause. sql statment select (select [dbo].[udf_readstaffmemberbasic](sm.staffmemberid) xml path ('staffmembersummary'), root ('items'), type ), count(sm.staffmemberid) totalresults, ceiling(cast(count(sm.staffmemberid) decimal)/ @pagesize) totalpages staffmember sm inner join staffmembertoadditionalrole ar on sm.staffmemberid = ar.staffmemberid (sm.firstname '%' + @name + '%' or sm.surname '%' + @name + '%') , (@floorid null or sm.floorid = @floorid) , (@directorateid null or sm.directorateid = @directorateid) , (@additionalroleid null or ar.additionalroleid = @additionalroleid) order sm.staffmemberid offset @page * @pagesize rows fe...
Read more

Angularjs unit testing - ng-disabled not working when adding text to textarea -

-
i trying test angularjs component using karma, mocha, power-assert. have textarea , button in component, button disabled based on length of text in textarea. when run component in browser works perfectly. can't figure out how test functionality. here's bit of code. inquiryform.js function inquiryform($scope) { // plan add logic here } angular.module('myapp').component('inquiryform', { controller: inquiryform, controlleras: 'inquiryform', templateurl: 'inquiryform.html' }); inquiryform.html <div class="contact"> <div>thanks contacting us.</div> <form> <textarea ng-model="inquiryform.inquirytext" name=""></textarea> <input type="submit" value="send" ng-disabled="!inquiryform.inquirytext.length"> </form> </div> inquiryformtest.js describe('inquiry form ', () => { let $r...
Read more

How to start daemon on android by adb -

-
can me please, head swollen... i trying run daemon on android emu/device command: adb -s <device_name> shell su -c /dir/daemon <port_number> but nothink happens, , no errors! if do: adb -s <device> shell and form shell cmdline: su -c /dir/daemon <port_number> than work fine. try use shell-script , run: adb -s <device_name> shell sh su -c /dir/script.sh <port_number> and try generate script qt code port number , use: adb -s <device_name> shell sh su -c /dir/script.sh but not helped... problem if enter adb shell previous run daemon - work. problem on different device/emu/iso_image different command format not work. example: adb -s <device_name> shell su -c /dir/daemon <port_number> // work @ emu, not @ iso and vice: adb -s <device_name> shell su -c "/dir/daemon <port_number>" // work @ iso etc. everybody can answer what's matter? sorry english adb shell su -c ...
Read more