blocks|key|1202404|text|在express.js+(自第3版起)中，您应该使用该语法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1202405|var+fs+=+require('fs');
var+http+=+require('http');
var+https+=+require('https');
var+privateKey++=+fs.readFileSync('sslcert/server.key',+'utf8');
var+certificate+=+fs.readFileSync('sslcert/server.crt',+'utf8');

var+credentials+=+{key:+privateKey,+cert:+certificate};
var+express+=+require('express');
var+app+=+express();

//+your+express+configuration+here

var+httpServer+=+http.createServer(app);
var+httpsServer+=+https.createServer(credentials,+app);

httpServer.listen(8080);
httpsServer.listen(8443);|code-block|syntax|javascript|1202406|这样，您就可以向本机http/https服务器提供快速中间件。|1202407|如果您希望应用程序在1024以下的端口上运行，则需要使用sudo命令(不建议使用)或使用反向代理(例如，nginx、haproxy)。|offset|length|style|CODE|1202408|entityMap^0|0|0|0|S|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

In express.js (since version 3) you should use that syntax:

<pre class="lang-js prettyprint-override"><code>var fs = require('fs');
var http = require('http');
var https = require('https');
var privateKey = fs.readFileSync('sslcert/server.key', 'utf8');
var certificate = fs.readFileSync('sslcert/server.crt', 'utf8');

var credentials = {key: privateKey, cert: certificate};
var express = require('express');
var app = express();

// your express configuration here

var httpServer = http.createServer(app);
var httpsServer = https.createServer(credentials, app);

httpServer.listen(8080);
httpsServer.listen(8443);
</code></pre>

In that way you provide express middleware to the native http/https server

If you want your app running on ports below 1024, you will need to use <code>sudo</code> command (not recommended) or use a reverse proxy (e.g. nginx, haproxy).

blocks|key|1680270|text|在让SSL在端口443以外的端口上工作时，我遇到了类似的问题。在我的例子中，我有一个捆绑证书以及一个证书和一个密钥。包证书是一个包含多个证书的文件，节点要求将这些证书分解为数组中的单独元素。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1680271|++++var+express+=+require('express');
++++var+https+=+require('https');
++++var+fs+=+require('fs');

++++var+options+=+{
++++++ca:+[fs.readFileSync(PATH_TO_BUNDLE_CERT_1),+fs.readFileSync(PATH_TO_BUNDLE_CERT_2)],
++++++cert:+fs.readFileSync(PATH_TO_CERT),
++++++key:+fs.readFileSync(PATH_TO_KEY)
++++};

++++app+=+express()

++++app.get('/',+function(req,res)+{
++++++++res.send('hello');
++++});

++++var+server+=+https.createServer(options,+app);

++++server.listen(8001,+function(){
++++++++console.log("server+running+at+https://IP_ADDRESS:8001/")
++++});|code-block|syntax|javascript|1680272|在app.js中，您需要指定https并相应地创建服务器。另外，确保您试图使用的端口实际上允许入站通信量。|1680273|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I ran into a similar issue with getting SSL to work on a port other than port 443. In my case I had a bundle certificate as well as a certificate and a key. The bundle certificate is a file that holds multiple certificates, node requires that you break those certificates into separate elements of an array. 

<pre><code> var express = require('express');
 var https = require('https');
 var fs = require('fs');

 var options = {
 ca: [fs.readFileSync(PATH_TO_BUNDLE_CERT_1), fs.readFileSync(PATH_TO_BUNDLE_CERT_2)],
 cert: fs.readFileSync(PATH_TO_CERT),
 key: fs.readFileSync(PATH_TO_KEY)
 };

 app = express()

 app.get('/', function(req,res) {
 res.send('hello');
 });

 var server = https.createServer(options, app);

 server.listen(8001, function(){
 console.log("server running at https://IP_ADDRESS:8001/")
 });
</code></pre>

In app.js you need to specify https and create the server accordingly. Also, make sure that the port you're trying to use is actually allowing inbound traffic.

blocks|key|1202455|text|包括各点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1202456|SSL设置|ordered-list-item|1202457|在config/local.js中|1202458|在config/env/production.js中|1202459|1202460|​|1202461|HTTP和WS处理|1202462|在开发过程中，应用程序必须在HTTP上运行，这样我们就可以轻松地调试我们的应用程序。|1202463|出于安全考虑，该应用程序必须在生产中在HTTPS上运行。|1202464|应用程序生产HTTP请求应该始终重定向到https。|1202465|SSL配置|1202466|在Sailsjs中，有两种配置所有内容的方法，第一种是在配置文件夹中配置每个文件，每个文件都有各自的文件(就像connections.js中有关设置的数据库连接)。第二，配置环境基文件结构，每个环境文件显示在config/env文件夹中，每个文件包含特定env的设置。|offset|length|style|CODE|1202467|Sails首先查找config/env文件夹，然后期待config/+*.js|BOLD|1202468|现在让我们在config/local.js__中安装ssl。|1202469|var+local+=+{
+++port:+process.env.PORT+%7C%7C+1337,
+++environment:+process.env.NODE_ENV+%7C%7C+'development'
};

if+(process.env.NODE_ENV+==+'production')+{
++++local.ssl+=+{
++++++++secureProtocol:+'SSLv23_method',
++++++++secureOptions:+require('constants').SSL_OP_NO_SSLv3,
++++++++ca:+require('fs').readFileSync(__dirname+%2B+'/path/to/ca.crt','ascii'),
++++++++key:+require('fs').readFileSync(__dirname+%2B+'/path/to/jsbot.key','ascii'),
++++++++cert:+require('fs').readFileSync(__dirname+%2B+'/path/to/jsbot.crt','ascii')
++++};
++++local.port+=+443;+//+This+port+should+be+different+than+your+default+port
}

module.exports+=+local;|code-block|syntax|javascript|1202470|您也可以在config/env/production.js中添加此选项。(这个片段还展示了如何处理多个CARoot+certi)|blockquote|1202471|或在production.js中|1202472|module.exports+=+{
++++port:+443,
++++ssl:+{
++++++++secureProtocol:+'SSLv23_method',
++++++++secureOptions:+require('constants').SSL_OP_NO_SSLv3,
++++++++ca:+[
++++++++++++require('fs').readFileSync(__dirname+%2B+'/path/to/AddTrustExternalCARoot.crt',+'ascii'),
++++++++++++require('fs').readFileSync(__dirname+%2B+'/path/to/COMODORSAAddTrustCA.crt',+'ascii'),
++++++++++++require('fs').readFileSync(__dirname+%2B+'/path/to/COMODORSADomainValidationSecureServerCA.crt',+'ascii')
++++++++],
++++++++key:+require('fs').readFileSync(__dirname+%2B+'/path/to/jsbot.key',+'ascii'),
++++++++cert:+require('fs').readFileSync(__dirname+%2B+'/path/to/jsbot.crt',+'ascii')
++++}
};|1202473|http/https+&+ws/wss重定向|1202474|在这里，ws是Web套接字，wss代表安全的Web套接字，因为我们设置了ssl，这时http和ws都变得安全，并分别转换为https和wss。|1202475|我们的应用程序有很多来源会收到请求，就像任何博客文章、社交媒体帖子一样，但是我们的服务器只运行在https上，所以当任何请求来自http时，都会在客户端浏览器中出现“这个站点无法到达”错误。我们失去了我们的网站流量。因此，我们必须将http请求重定向到https，同样的规则允许使用websocket，否则套接字将失败。|1202476|因此，我们需要在端口80+(http)上运行相同的服务器，并将所有请求转移到端口443(https)。在提升服务器之前，Sails首先编译config/bootstrap.js文件。在这里，我们可以在端口80上启动我们的快速服务器。|1202477|In+config/bootstrap.js+(创建http服务器并将所有请求重定向到https)|1202478|module.exports.bootstrap+=+function(cb)+{
++++var+express+=+require("express"),
++++++++app+=+express();

++++app.get('*',+function(req,+res)+{++
++++++++if+(req.isSocket)+
++++++++++++return+res.redirect('wss://'+%2B+req.headers.host+%2B+req.url)++

++++++++return+res.redirect('https://'+%2B+req.headers.host+%2B+req.url)++
++++}).listen(80);
++++cb();
};|1202479|现在您可以访问http://www.yourdomain.com了，它将重定向到https://www.yourdomain.com|1202480|entityMap|0|LINK|mutability|MUTABLE|url|http://www.yourdomain.com/|1|https://www.yourdomain.com/^0|0|1|1|1|0|0|0|0|0|0|0|2W|A|0|0|13|0|6|F|0|0|5|O|0|2|D|0|0|0|0|0|0|0|1D|0|0|7|P|0|14|Q|1|0^^$0|@$1|2|3|4|5|6|7|26|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|27|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|28|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|29|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|2B|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2C|8|@]|9|@]|A|$]]|$1|N|3|O|5|D|7|2D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|D|7|2E|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|2F|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|2G|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2H|8|@$X|2I|Y|2J|Z|10]]|9|@]|A|$]]|$1|11|3|12|5|6|7|2K|8|@$X|2L|Y|2M|Z|13]]|9|@]|A|$]]|$1|14|3|15|5|6|7|2N|8|@$X|2O|Y|2P|Z|10]]|9|@]|A|$]]|$1|16|3|17|5|18|7|2Q|8|@]|9|@]|A|$19|1A]]|$1|1B|3|1C|5|1D|7|2R|8|@$X|2S|Y|2T|Z|13]]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2U|8|@$X|2V|Y|2W|Z|13]]|9|@]|A|$]]|$1|1G|3|1H|5|18|7|2X|8|@]|9|@]|A|$19|1A]]|$1|1I|3|1J|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|30|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|31|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|32|8|@$X|33|Y|34|Z|13]]|9|@]|A|$]]|$1|1S|3|1T|5|18|7|35|8|@]|9|@]|A|$19|1A]]|$1|1U|3|1V|5|1D|7|36|8|@]|9|@$X|37|Y|38|1|39]|$X|3A|Y|3B|1|3C]]|A|$]]|$1|1W|3|-4|5|6|7|3D|8|@]|9|@]|A|$]]]|1X|$1Y|$5|1Z|20|21|A|$22|23]]|24|$5|1Z|20|21|A|$22|25]]]]

<h3>Including Points:</h3>

<ol>
<li>SSL setup 

<ol>
<li>In config/local.js </li>
<li>In config/env/production.js</li>
</ol></li>
</ol>

<h3>HTTP and WS handling</h3>

<ol>
<li>The app must run on HTTP in development so we can easily debug our
app. </li>
<li>The app must run on HTTPS in production for security concern.</li>
<li>App production HTTP request should always redirect to https.</li>
</ol>

<h1>SSL configuration</h1>

In Sailsjs there are two ways to configure all the stuff, first is to configure in config folder with each one has their separate files (like database connection regarding settings lies within connections.js ). And second is configure on environment base file structure, each environment files presents in <code>config/env</code> folder and each file contains settings for particular env.

Sails first looks in config/env folder and then look forward to config/ *.js

Now lets setup ssl in <code>config/local.js</code>.

<pre><code>var local = {
 port: process.env.PORT || 1337,
 environment: process.env.NODE_ENV || 'development'
};

if (process.env.NODE_ENV == 'production') {
 local.ssl = {
 secureProtocol: 'SSLv23_method',
 secureOptions: require('constants').SSL_OP_NO_SSLv3,
 ca: require('fs').readFileSync(__dirname + '/path/to/ca.crt','ascii'),
 key: require('fs').readFileSync(__dirname + '/path/to/jsbot.key','ascii'),
 cert: require('fs').readFileSync(__dirname + '/path/to/jsbot.crt','ascii')
 };
 local.port = 443; // This port should be different than your default port
}

module.exports = local;
</code></pre>

<blockquote>
 Alternative you can add this in config/env/production.js too. (This snippet also show how to handle multiple CARoot certi)
</blockquote>

Or in production.js

<pre><code>module.exports = {
 port: 443,
 ssl: {
 secureProtocol: 'SSLv23_method',
 secureOptions: require('constants').SSL_OP_NO_SSLv3,
 ca: [
 require('fs').readFileSync(__dirname + '/path/to/AddTrustExternalCARoot.crt', 'ascii'),
 require('fs').readFileSync(__dirname + '/path/to/COMODORSAAddTrustCA.crt', 'ascii'),
 require('fs').readFileSync(__dirname + '/path/to/COMODORSADomainValidationSecureServerCA.crt', 'ascii')
 ],
 key: require('fs').readFileSync(__dirname + '/path/to/jsbot.key', 'ascii'),
 cert: require('fs').readFileSync(__dirname + '/path/to/jsbot.crt', 'ascii')
 }
};
</code></pre>

<h1>http/https &amp; ws/wss redirection</h1>

Here ws is Web Socket and wss represent Secure Web Socket, as we set up ssl then now http and ws both requests become secure and transform to https and wss respectively.

There are many source from our app will receive request like any blog post, social media post but our server runs only on https so when any request come from http it gives “This site can’t be reached” error in client browser. And we loss our website traffic. So we must redirect http request to https, same rules allow for websocket otherwise socket will fails.

So we need to run same server on port 80 (http), and divert all request to port 443(https). Sails first compile config/bootstrap.js file before lifting server. Here we can start our express server on port 80.

In config/bootstrap.js (Create http server and redirect all request to https)

<pre><code>module.exports.bootstrap = function(cb) {
 var express = require("express"),
 app = express();

 app.get('*', function(req, res) { 
 if (req.isSocket) 
 return res.redirect('wss://' + req.headers.host + req.url) 

 return res.redirect('https://' + req.headers.host + req.url) 
 }).listen(80);
 cb();
};
</code></pre>

<blockquote>
 Now you can visit <a href="http://www.yourdomain.com" rel="noreferrer">http://www.yourdomain.com</a>, it will redirect to <a href="https://www.yourdomain.com" rel="noreferrer">https://www.yourdomain.com</a>
</blockquote>

blocks|key|1202486|text|这就是我的工作方式。所使用的重定向也将重定向所有正常的http。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1202487|const+express+=+require('express');
const+bodyParser+=+require('body-parser');
const+path+=+require('path');
const+http+=+require('http');
const+app+=+express();
var+request+=+require('request');
//For+https
const+https+=+require('https');
var+fs+=+require('fs');
var+options+=+{
++key:+fs.readFileSync('certificates/private.key'),
++cert:+fs.readFileSync('certificates/certificate.crt'),
++ca:+fs.readFileSync('certificates/ca_bundle.crt')
};

//+API+file+for+interacting+with+MongoDB
const+api+=+require('./server/routes/api');

//+Parsers
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({+extended:+false+}));

//+Angular+DIST+output+folder
app.use(express.static(path.join(__dirname,+'dist')));

//+API+location
app.use('/api',+api);

//+Send+all+other+requests+to+the+Angular+app
app.get('*',+(req,+res)+=>+{
++res.sendFile(path.join(__dirname,+'dist/index.html'));
});
app.use(function(req,resp,next){
++if+(req.headers['x-forwarded-proto']+==+'http')+{
++++++return+resp.redirect(301,+'https://'+%2B+req.headers.host+%2B+'/');
++}+else+{
++++++return+next();
++}
});


http.createServer(app).listen(80)
https.createServer(options,+app).listen(443);|code-block|syntax|javascript|1202488|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is how its working for me. The redirection used will redirect all the normal http as well.

<pre><code>const express = require('express');
const bodyParser = require('body-parser');
const path = require('path');
const http = require('http');
const app = express();
var request = require('request');
//For https
const https = require('https');
var fs = require('fs');
var options = {
 key: fs.readFileSync('certificates/private.key'),
 cert: fs.readFileSync('certificates/certificate.crt'),
 ca: fs.readFileSync('certificates/ca_bundle.crt')
};

// API file for interacting with MongoDB
const api = require('./server/routes/api');

// Parsers
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));

// Angular DIST output folder
app.use(express.static(path.join(__dirname, 'dist')));

// API location
app.use('/api', api);

// Send all other requests to the Angular app
app.get('*', (req, res) =&gt; {
 res.sendFile(path.join(__dirname, 'dist/index.html'));
});
app.use(function(req,resp,next){
 if (req.headers['x-forwarded-proto'] == 'http') {
 return resp.redirect(301, 'https://' + req.headers.host + '/');
 } else {
 return next();
 }
});


http.createServer(app).listen(80)
https.createServer(options, app).listen(443);
</code></pre>

blocks|key|1202622|text|使用绿色锁-快递:免费SSL，自动HTTPS|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1202623|格林洛克处理证书颁发和更新(通过我们加密)和http+=>+https重定向，跳出框。|offset|length|1202624|express-app.js|style|CODE|1202625|var+express+=+require('express');
var+app+=+express();

app.use('/',+function+(req,+res)+{
++res.send({+msg:+"Hello,+Encrypted+World!"+})
});

//+DO+NOT+DO+app.listen()
//+Instead+export+your+app:
module.exports+=+app;|code-block|syntax|javascript|1202626|server.js|1202627|require('greenlock-express').create({
++//+Let's+Encrypt+v2+is+ACME+draft+11
++version:+'draft-11'
,+server:+'https://acme-v02.api.letsencrypt.org/directory'

++//+You+MUST+change+these+to+valid+email+and+domains
,+email:+'john.doe@example.com'
,+approveDomains:+[+'example.com',+'www.example.com'+]
,+agreeTos:+true
,+configDir:+"/path/to/project/acme/"

,+app:+require('./express-app.j')

,+communityMember:+true+//+Get+notified+of+important+updates
,+telemetry:+true+++++++//+Contribute+telemetry+data+to+the+project
}).listen(80,+443);|1202628|屏风|1202629|观看QuickStart演示：https://youtu.be/e8vaR4CEZ5s|1202630|​|1202631|📷|atomic|1202632|1202633|本地主机|1202634|只是提前回答，因为这是一个常见的后续问题：|1202635|本地主机上不能有SSL证书。然而，您可以使用类似天线位的东西，这将允许您作为真实的本地应用程序运行。|1202636|您也可以使用Greenlock通过DNS-01挑战私有域，这是在自述的自述和支持它的各种插件。|1202637|非标准港口(即第80+/443号)|1202638|阅读上面关于localhost的说明--我们也不能使用非标准端口来加密。|1202639|但是，您可以通过端口转发、SNI路由将内部非标准端口公开为外部标准端口，或者使用像Telebit这样的方式为您进行SNI路由和端口转发/中继。|1202640|您也可以使用DNS-01挑战，在这种情况下，您根本不需要公开端口，您也可以通过这种方式保护专用网络上的域。|1202641|entityMap|0|LINK|mutability|MUTABLE|url|https://git.coolaj86.com/coolaj86/greenlock-express.js|1|https://youtu.be/e8vaR4CEZ5s|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/f16d4c5c6bdba8dda27d79718f3a51b8.png|imageAlt|3|https://git.coolaj86.com/coolaj86/telebit.js^0|0|0|4|0|0|0|E|0|0|0|9|0|0|0|F|S|1|0|0|0|1|2|0|0|0|0|O|3|3|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@$D|22|E|23|1|24]]|A|$]]|$1|F|3|G|5|6|7|25|8|@$D|26|E|27|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|28|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|29|8|@$D|2A|E|2B|H|I]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|2C|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|2D|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2E|8|@]|9|@$D|2F|E|2G|1|2H]]|A|$]]|$1|W|3|X|5|6|7|2I|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|2J|8|@]|9|@$D|2K|E|2L|1|2M]]|A|$]]|$1|11|3|X|5|6|7|2N|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2O|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2P|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2Q|8|@]|9|@$D|2R|E|2S|1|2T]]|A|$]]|$1|18|3|19|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2W|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2X|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]]|1J|$1K|$5|1L|1M|1N|A|$1O|1P]]|1Q|$5|1L|1M|1N|A|$1O|1R]]|1S|$5|1T|1M|1U|A|$1V|1W|1X|-4]]|1Y|$5|1L|1M|1N|A|$1O|1Z]]]]

<h1>Use greenlock-express: Free SSL, Automated HTTPS</h1>

<a href="https://git.coolaj86.com/coolaj86/greenlock-express.js" rel="noreferrer">Greenlock</a> handles certificate issuance and renewal (via Let's Encrypt) and http => https redirection, out-of-the box.

<code>express-app.js</code>:

<pre><code>var express = require('express');
var app = express();

app.use('/', function (req, res) {
 res.send({ msg: "Hello, Encrypted World!" })
});

// DO NOT DO app.listen()
// Instead export your app:
module.exports = app;
</code></pre>

<code>server.js</code>:

<pre><code>require('greenlock-express').create({
 // Let's Encrypt v2 is ACME draft 11
 version: 'draft-11'
, server: 'https://acme-v02.api.letsencrypt.org/directory'

 // You MUST change these to valid email and domains
, email: 'john.doe@example.com'
, approveDomains: [ 'example.com', 'www.example.com' ]
, agreeTos: true
, configDir: "/path/to/project/acme/"

, app: require('./express-app.j')

, communityMember: true // Get notified of important updates
, telemetry: true // Contribute telemetry data to the project
}).listen(80, 443);
</code></pre>

<h1>Screencast</h1>

Watch the QuickStart demonstration: <a href="https://youtu.be/e8vaR4CEZ5s" rel="noreferrer">https://youtu.be/e8vaR4CEZ5s</a>

<a href="https://youtu.be/e8vaR4CEZ5s" rel="noreferrer"><img src="https://i.imgur.com/Y8ix6Ts.png" alt=""></a>

<h1>For Localhost</h1>

Just answering this ahead-of-time because it's a common follow-up question:

You can't have SSL certificates on localhost. However, you can use something like <a href="https://git.coolaj86.com/coolaj86/telebit.js" rel="noreferrer">Telebit</a> which will allow you to run local apps as real ones.

You can also use private domains with Greenlock via DNS-01 challenges, which is mentioned in the README along with various plugins which support it.

<h1>Non-standard Ports (i.e. no 80 / 443)</h1>

Read the note above about localhost - you can't use non-standard ports with Let's Encrypt either.

However, you can expose your internal non-standard ports as external standard ports via port-forward, sni-route, or use something like Telebit that does SNI-routing and port-forwarding / relaying for you.

You can also use DNS-01 challenges in which case you won't need to expose ports at all and you can also secure domains on private networks this way.

blocks|key|1680489|text|这是我的工作代码，用于速成4.0。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1680490|Exchange4.0与3.0和其他语言有很大的不同。|1680491|4.0您有/bin/www文件，您将在这里添加https。|1680492|"npm“是启动快递4.0服务器的标准方式。|1680493|readFileSync()函数应该使用__dirname+get当前目录|1680494|虽然需要()，但使用./指的是当前目录。|1680495|首先将private.key和public.cert文件放在/bin文件夹下，它与WWW文件__相同。|1680496|entityMap^0|4|4|B|5|0|0|0|0|K|9|0|6|6|0|0|1A|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|S|$]]

This is my working code for express 4.0.

express 4.0 is very different from 3.0 and others. 

4.0 you have /bin/www file, which you are going to add https here.

"npm start" is standard way you start express 4.0 server.

readFileSync() function should use __dirname get current directory

while require() use ./ refer to current directory.

First you put private.key and public.cert file under /bin folder, 
It is same folder as WWW file.

blocks|key|1680536|text|首先，您需要创建selfsigned.key和selfsigned.crt文件。转到创建自签名SSL证书。或执行以下步骤。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1680537|转到终端并运行以下命令。|1680538|sudo+openssl+req+-x509+-nodes+-days+365+-newkey+rsa:2048+-keyout+./selfsigned.key+-out+selfsigned.crt|CODE|1680539|之后，输入以下信息|unordered-list-item|1680540|国家名称(2个字母代码)+AU：US|1680541|州或省名称(全名)一些州：纽约|1680542|地方名称(如，城市)+[]:NY|1680543|组织名称(如公司)互联网Widgits+Pty+Ltd：xyz+(您的组织)|1680544|组织单位名称(例如，节)+[]：xyz+(您的单位名称)|1680545|公共名称(例如，服务器FQDN或您的名称)+[]：www.xyz.com+(您的网址)|1680546|电子邮件地址[]：您的电子邮件|1680547|创建之后，在代码中添加key+&+cert文件，并将选项传递给服务器。|blockquote|1680548|const+express+=+require('express');
const+https+=+require('https');
const+fs+=+require('fs');
const+port+=+3000;

var+key+=+fs.readFileSync(__dirname+%2B+'/../certs/selfsigned.key');
var+cert+=+fs.readFileSync(__dirname+%2B+'/../certs/selfsigned.crt');
var+options+=+{
++key:+key,
++cert:+cert
};

app+=+express()
app.get('/',+(req,+res)+=>+{
+++res.send('Now+using+https..');
});

var+server+=+https.createServer(options,+app);

server.listen(port,+()+=>+{
++console.log("server+starting+on+port+:+"+%2B+port)
});|code-block|syntax|javascript|1680549|最后，使用https运行应用程序。|1680550|更多信息https://github.com/sagardere/set-up-SSL-in-nodejs|1680551|entityMap|0|LINK|mutability|MUTABLE|url|https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-apache-in-ubuntu-16-04|1|https://github.com/sagardere/set-up-SSL-in-nodejs^0|8|E|N|E|16|B|0|0|0|0|2T|0|0|G|2|0|D|2|0|E|2|0|S|A|0|G|C|0|P|I|0|9|6|0|0|0|5|5|0|4|1D|1|0^^$0|@$1|2|3|4|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]]|D|@$9|1S|A|1T|1|1U]]|E|$]]|$1|F|3|G|5|6|7|1V|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1W|8|@$9|1X|A|1Y|B|J]]|D|@]|E|$]]|$1|K|3|L|5|M|7|1Z|8|@]|D|@]|E|$]]|$1|N|3|O|5|M|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|M|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|R|3|S|5|M|7|26|8|@$9|27|A|28|B|C]]|D|@]|E|$]]|$1|T|3|U|5|M|7|29|8|@$9|2A|A|2B|B|C]]|D|@]|E|$]]|$1|V|3|W|5|M|7|2C|8|@$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|M|7|2F|8|@$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|M|7|2I|8|@$9|2J|A|2K|B|C]]|D|@]|E|$]]|$1|11|3|12|5|13|7|2L|8|@]|D|@]|E|$]]|$1|14|3|15|5|16|7|2M|8|@]|D|@]|E|$17|18]]|$1|19|3|1A|5|M|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|1B|3|1C|5|13|7|2Q|8|@]|D|@$9|2R|A|2S|1|2T]]|E|$]]|$1|1D|3|-4|5|6|7|2U|8|@]|D|@]|E|$]]]|1E|$1F|$5|1G|1H|1I|E|$1J|1K]]|1L|$5|1G|1H|1I|E|$1J|1M]]]]

First, you need to create selfsigned.key and selfsigned.crt files. 
Go to <a href="https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-apache-in-ubuntu-16-04" rel="noreferrer">Create a Self-Signed SSL Certificate</a> Or do following steps.

Go to the terminal and run the following command.

<code>sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ./selfsigned.key -out selfsigned.crt</code>

<ul>
<li>After that put the following information</li>
<li>Country Name (2 letter code) [AU]: US</li>
<li>State or Province Name (full name) [Some-State]: NY</li>
<li>Locality Name (eg, city) []:NY</li>
<li>Organization Name (eg, company) [Internet Widgits Pty Ltd]: xyz (Your - Organization)</li>
<li>Organizational Unit Name (eg, section) []: xyz (Your Unit Name) </li>
<li>Common Name (e.g. server FQDN or YOUR name) []: www.xyz.com (Your URL)</li>
<li>Email Address []: Your email</li>
</ul>

<blockquote>
 After creation adds key &amp; cert file in your code, and pass the options to the server.
</blockquote>

<pre><code>const express = require('express');
const https = require('https');
const fs = require('fs');
const port = 3000;

var key = fs.readFileSync(__dirname + '/../certs/selfsigned.key');
var cert = fs.readFileSync(__dirname + '/../certs/selfsigned.crt');
var options = {
 key: key,
 cert: cert
};

app = express()
app.get('/', (req, res) =&gt; {
 res.send('Now using https..');
});

var server = https.createServer(options, app);

server.listen(port, () =&gt; {
 console.log("server starting on port : " + port)
});
</code></pre>

<ul>
<li>Finally run your application using https.</li>
</ul>

<blockquote>
 More information <a href="https://github.com/sagardere/set-up-SSL-in-nodejs" rel="noreferrer">https://github.com/sagardere/set-up-SSL-in-nodejs</a>
</blockquote>

blocks|key|1202792|text|别忘了你在证书上的PEM通行证短语！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1202793|使用OpenSSL生成凭据时(不要忘记-sha256标志)：|offset|length|style|CODE|1202794|OpenSSL>+req+-x509+-sha256+-newkey+rsa:4096+-keyout+key.pem+-out+cert.pem+-days+365
Generating+a+RSA+private+key

writing+new+private+key+to+'key.pem'
Enter+PEM+pass+phrase:
Verifying+-+Enter+PEM+pass+phrase:|code-block|syntax|javascript|1202795|您的JS/TS代码：|1202796|const+credentials+=+{key:+privateKey,+cert:+certificate,+passphrase:+'YOUR+passphrase'};|1202797|参考文献|1202798|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/54171490/14223224^0|0|J|7|0|0|0|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

Don't forget your PEM pass phrase in the credentials !
When you generate your credentials with OpenSSL (don't forget the <code>-sha256</code> flag) :
<pre><code>OpenSSL&gt; req -x509 -sha256 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365
Generating a RSA private key

writing new private key to 'key.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
</code></pre>
Your JS/TS code :
<pre><code>const credentials = {key: privateKey, cert: certificate, passphrase: 'YOUR passphrase'};
</code></pre>
<a href="https://stackoverflow.com/a/54171490/14223224">Reference</a>

blocks|key|1680702|text|这个答案非常类似于but酶，但它适用于LetsEncrypt+(Ubuntu)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1680703|//+Dependencies
const+fs+=+require('fs');
const+http+=+require('http');
const+https+=+require('https');
const+express+=+require('express');

const+app+=+express();

//+Certificate
const+privateKey+=+fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/privkey.pem',+'utf8');
const+certificate+=+fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/cert.pem',+'utf8');
const+ca+=+fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/chain.pem',+'utf8');

const+credentials+=+{
++++key:+privateKey,
++++cert:+certificate,
++++ca:+ca
};

app.use((req,+res)+=>+{
++++res.send('Hello+there+!');
});

//+Starting+both+http+&+https+servers
const+httpServer+=+http.createServer(app);
const+httpsServer+=+https.createServer(credentials,+app);

httpServer.listen(80,+()+=>+{
++++console.log('HTTP+Server+running+on+port+80');
});

httpsServer.listen(443,+()+=>+{
++++console.log('HTTPS+Server+running+on+port+443');
});|code-block|syntax|javascript|1680704|您可能会遇到:+EACCES:权限被拒绝，打开'/etc/letsencrypt/live/yourdeomain.com/privkey.pem‘|1680705|答案在这里：让我们从错误:+EACCES:权限拒绝开始加密SSL，打开'/etc/letsencrypt/live/domain.net/privkey.pem'“|1680706|对我有用的是在ubuntu终端获取用户whoami中。|CODE|1680707|//+Create+group+with+root+and+nodeuser+as+members
$+sudo+addgroup+nodecert
$+sudo+adduser+ubuntu+nodecert
$+sudo+adduser+root+nodecert

//+Make+the+relevant+letsencrypt+folders+owned+by+said+group.
$+sudo+chgrp+-R+nodecert+/etc/letsencrypt/live
$+sudo+chgrp+-R+nodecert+/etc/letsencrypt/archive

//+Allow+group+to+open+relevant+folders
$+sudo+chmod+-R+750+/etc/letsencrypt/live
$+sudo+chmod+-R+750+/etc/letsencrypt/archive

sudo+reboot|1680708|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/48078083/lets-encrypt-ssl-couldnt-start-by-error-eacces-permission-denied-open-et^0|J|K|0|0|0|6|24|0|0|J|6|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|O|3|P|5|6|7|1A|8|@$9|1B|A|1C|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|T|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]]]

This answer is very similar to Setthase but its for LetsEncrypt (Ubuntu)
<pre><code>// Dependencies
const fs = require('fs');
const http = require('http');
const https = require('https');
const express = require('express');

const app = express();

// Certificate
const privateKey = fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/privkey.pem', 'utf8');
const certificate = fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/cert.pem', 'utf8');
const ca = fs.readFileSync('/etc/letsencrypt/live/yourdomain.com/chain.pem', 'utf8');

const credentials = {
 key: privateKey,
 cert: certificate,
 ca: ca
};

app.use((req, res) =&gt; {
 res.send('Hello there !');
});

// Starting both http &amp; https servers
const httpServer = http.createServer(app);
const httpsServer = https.createServer(credentials, app);

httpServer.listen(80, () =&gt; {
 console.log('HTTP Server running on port 80');
});

httpsServer.listen(443, () =&gt; {
 console.log('HTTPS Server running on port 443');
});
</code></pre>
You might encounter : EACCES: permission denied, open '/etc/letsencrypt/live/yourdeomain.com/privkey.pem'
The answer to that is here : <a href="https://stackoverflow.com/questions/48078083/lets-encrypt-ssl-couldnt-start-by-error-eacces-permission-denied-open-et">Let&#39;s encrypt SSL couldn&#39;t start by &quot;Error: EACCES: permission denied, open &#39;/etc/letsencrypt/live/domain.net/privkey.pem&#39;&quot;</a>
What worked for me is this in ubuntu ssh terminal
Get user <code>whoami</code>
<pre><code>// Create group with root and nodeuser as members
$ sudo addgroup nodecert
$ sudo adduser ubuntu nodecert
$ sudo adduser root nodecert

// Make the relevant letsencrypt folders owned by said group.
$ sudo chgrp -R nodecert /etc/letsencrypt/live
$ sudo chgrp -R nodecert /etc/letsencrypt/archive

// Allow group to open relevant folders
$ sudo chmod -R 750 /etc/letsencrypt/live
$ sudo chmod -R 750 /etc/letsencrypt/archive

sudo reboot
</code></pre>

blocks|key|1202838|text|还可以使用node-forge生成自签名证书。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1202839|在下面的代码中，在启动时生成一个新的证书，这意味着每次重新启动服务器时都会得到一个新的证书。|1202840|const+https+=+require('https')
const+express+=+require('express')
const+forge+=+require('node-forge')


;(function+main()+{
++const+server+=+https.createServer(
++++generateX509Certificate([
++++++{+type:+6,+value:+'http://localhost'+},
++++++{+type:+7,+ip:+'127.0.0.1'+}
++++]),+
++++makeExpressApp()
++)
++server.listen(8443,+()+=>+{
++++console.log('Listening+on+https://localhost:8443/')
++})
})()


function+generateX509Certificate(altNames)+{
++const+issuer+=+[
++++{+name:+'commonName',+value:+'example.com'+},
++++{+name:+'organizationName',+value:+'E+Corp'+},
++++{+name:+'organizationalUnitName',+value:+'Washington+Township+Plant'+}
++]
++const+certificateExtensions+=+[
++++{+name:+'basicConstraints',+cA:+true+},
++++{+name:+'keyUsage',+keyCertSign:+true,+digitalSignature:+true,+nonRepudiation:+true,+keyEncipherment:+true,+dataEncipherment:+true+},
++++{+name:+'extKeyUsage',+serverAuth:+true,+clientAuth:+true,+codeSigning:+true,+emailProtection:+true,+timeStamping:+true+},
++++{+name:+'nsCertType',+client:+true,+server:+true,+email:+true,+objsign:+true,+sslCA:+true,+emailCA:+true,+objCA:+true+},
++++{+name:+'subjectAltName',+altNames+},
++++{+name:+'subjectKeyIdentifier'+}
++]
++const+keys+=+forge.pki.rsa.generateKeyPair(2048)
++const+cert+=+forge.pki.createCertificate()
++cert.validity.notBefore+=+new+Date()
++cert.validity.notAfter+=+new+Date()
++cert.validity.notAfter.setFullYear(cert.validity.notBefore.getFullYear()+%2B+1)
++cert.publicKey+=+keys.publicKey
++cert.setSubject(issuer)
++cert.setIssuer(issuer)
++cert.setExtensions(certificateExtensions)
++cert.sign(keys.privateKey)
++return+{
++++key:+forge.pki.privateKeyToPem(keys.privateKey),
++++cert:+forge.pki.certificateToPem(cert)
++}
}


function+makeExpressApp()+{
++const+app+=+express()
++app.get('/',+(req,+res)+=>+{
++++res.json({+message:+'Hello,+friend'+})
++})
++return+app
}|code-block|syntax|javascript|1202841|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/node-forge^0|5|A|5|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|11|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

<h4>You can also generate a self-signed certificate using <a href="https://www.npmjs.com/package/node-forge" rel="nofollow noreferrer"><code>node-forge</code></a></h4>
In the code below, a new certificate is generated on startup, which means you will get a new certificate every time you restart the server.
<pre class="lang-js prettyprint-override"><code>const https = require('https')
const express = require('express')
const forge = require('node-forge')


;(function main() {
 const server = https.createServer(
 generateX509Certificate([
 { type: 6, value: 'http://localhost' },
 { type: 7, ip: '127.0.0.1' }
 ]), 
 makeExpressApp()
 )
 server.listen(8443, () =&gt; {
 console.log('Listening on https://localhost:8443/')
 })
})()


function generateX509Certificate(altNames) {
 const issuer = [
 { name: 'commonName', value: 'example.com' },
 { name: 'organizationName', value: 'E Corp' },
 { name: 'organizationalUnitName', value: 'Washington Township Plant' }
 ]
 const certificateExtensions = [
 { name: 'basicConstraints', cA: true },
 { name: 'keyUsage', keyCertSign: true, digitalSignature: true, nonRepudiation: true, keyEncipherment: true, dataEncipherment: true },
 { name: 'extKeyUsage', serverAuth: true, clientAuth: true, codeSigning: true, emailProtection: true, timeStamping: true },
 { name: 'nsCertType', client: true, server: true, email: true, objsign: true, sslCA: true, emailCA: true, objCA: true },
 { name: 'subjectAltName', altNames },
 { name: 'subjectKeyIdentifier' }
 ]
 const keys = forge.pki.rsa.generateKeyPair(2048)
 const cert = forge.pki.createCertificate()
 cert.validity.notBefore = new Date()
 cert.validity.notAfter = new Date()
 cert.validity.notAfter.setFullYear(cert.validity.notBefore.getFullYear() + 1)
 cert.publicKey = keys.publicKey
 cert.setSubject(issuer)
 cert.setIssuer(issuer)
 cert.setExtensions(certificateExtensions)
 cert.sign(keys.privateKey)
 return {
 key: forge.pki.privateKeyToPem(keys.privateKey),
 cert: forge.pki.certificateToPem(cert)
 }
}


function makeExpressApp() {
 const app = express()
 app.get('/', (req, res) =&gt; {
 res.json({ message: 'Hello, friend' })
 })
 return app
}
</code></pre>

I'm trying to get HTTPS working on express.js for node, and I can't figure it out.
This is my <code>app.js</code> code.
<pre><code>var express = require('express');
var fs = require('fs');

var privateKey = fs.readFileSync('sslcert/server.key');
var certificate = fs.readFileSync('sslcert/server.crt');

var credentials = {key: privateKey, cert: certificate};


var app = express.createServer(credentials);

app.get('/', function(req,res) {
 res.send('hello');
});

app.listen(8000);
</code></pre>
When I run it, it seems to only respond to HTTP requests.
I wrote simple vanilla <code>node.js</code> based HTTPS app:
<pre><code>var fs = require(&quot;fs&quot;),
 http = require(&quot;https&quot;);

var privateKey = fs.readFileSync('sslcert/server.key').toString();
var certificate = fs.readFileSync('sslcert/server.crt').toString();

var credentials = {key: privateKey, cert: certificate};

var server = http.createServer(credentials,function (req, res) {
 res.writeHead(200, {'Content-Type': 'text/plain'});
 res.end('Hello World\n');
});

server.listen(8000);
</code></pre>
And when I run this app, it does respond to HTTPS requests. Note that I don't think the toString() on the fs result matters, as I've used combinations of both and still no es bueno.
<hr />
EDIT TO ADD:
For production systems, you're probably better off using Nginx or HAProxy to proxy requests to your nodejs app. You can set up nginx to handle the ssl requests and just speak http to your node app.js.
EDIT TO ADD (4/6/2015)
For systems on using AWS, you are better off using EC2 Elastic Load Balancers to handle SSL Termination, and allow regular HTTP traffic to your EC2 web servers. For further security, setup your security group such that only the ELB is allowed to send HTTP traffic to the EC2 instances, which will prevent external unencrypted HTTP traffic from hitting your machines.
<hr />

Enabling HTTPS on express.js

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我试图让HTTPS为节点在express.js上工作，但我无法弄清楚。这是我的app.js代码。var express = require('express');var fs = require('fs');var privateKey = fs.readFileSync('sslcert/server.key');v...

问在express.js上启用HTTPS
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在express.js上启用HTTPSEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在express.js上启用HTTPS
EN