Open awb99 opened 6 years ago
Let's encrypt only work on port 80 so that's a given.
In fact it does not even work there...
Trying to set it up like so:
var proxy = require('redbird')({
port: 80,
letsencrypt: {
path: "certs",
port: 3000
},
ssl: {
port: 443
}
});
proxy.register("www.example1.com", "http://localhost:4000", {
ssl: {
letsencrypt: {
email: "myemail",
production: false
}
}
})
All required ports (80, 3000) open on the machine. Result:
{"level":50,"time":1584348646276,"pid":17106,"hostname":"myhostnam","name":"redbird","code":"E_FAIL_DRY_CHALLENGE","msg":"Error registering LetsEncrypt certificates","stack":"Error: Error: Failed HTTP-01 Pre-Flight / Dry Run.\ncurl 'http://www.example1.com/.well-known/acme-challenge/test-11b20db3b14e697c64659191ab4b1d2c-0'\nExpected: 'test-11b20db3b14e697c64659191ab4b1d2c-0.vf_frPRC_B1SSKls4UADgdlSW0DwBbP92WcWfH0KOh0'\nGot: '<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p>The requested URL was not found on this server.</p>\n<p>Additionally, a 404 Not Found\nerror was encountered while trying to use an ErrorDocument to handle the request.</p>\n</body></html>\n'\nSee https://git.coolaj86.com/coolaj86/acme-v2.js/issues/4\n at /Users/decades/Documents/Node/test/node_modules/acme-v2/index.js:49:10\n at process._tickCallback (internal/process/next_tick.js:68:7)","type":"Error","v":1}
{"level":30,"time":1584348646276,"pid":17106,"hostname":"myhostname","name":"redbird","msg":"Could not get any certs for www.example1.com","v":1}
how could it work, do you control the example.com domain?
No of course not. Maybe I didn’t understand the entire stuff and what its all about with letsencrypt. Forget about
The below snipped works for port 80 for letsencrypt challlenges, but fails to work for port 180 for example.