plainPort usage? #6

Closed
opened 2019-10-30 16:31:12 +00:00 by Ghost · 3 comments

tl;dr: it seems ACME uses port 80 anyway, even though greenlock-express allows to set a different port.

Details

I'm trying to use a plain-port different from 80 (say, 8080). I want to have one application on port 80, another one on port 443.

The ACME Pre-Flight comes back with an error:

[acme-v2] handled(?) rejection as errback:
Error: Error: Failed HTTP-01 Pre-Flight / Dry Run.
curl 'http://test.example.net/.well-known/acme-challenge/test-d1d9a0f8…

(The actual hostname on the machine is not test.example.net.)

Obviously, ACME is trying to get the challenge from the application running on port 80, which replies with a 404 Not Found (in this case). On the other hand, if I run same the request ACME tries out, but using port 8080, I obtain the proper answer.

If I remove the application on port 80 and tells greenlock-express to use port 80, things work as expected.

tl;dr: it seems ACME uses port 80 anyway, even though `greenlock-express` allows to set a different port. Details ------- I'm trying to use a plain-port different from 80 (say, 8080). I want to have one application on port 80, another one on port 443. The ACME Pre-Flight comes back with an error: ``` [acme-v2] handled(?) rejection as errback: Error: Error: Failed HTTP-01 Pre-Flight / Dry Run. curl 'http://test.example.net/.well-known/acme-challenge/test-d1d9a0f8… ``` (The actual hostname on the machine is _not_ `test.example.net`.) Obviously, ACME is trying to get the challenge from the application running on port 80, which replies with a 404 Not Found (in this case). On the other hand, if I run same the request ACME tries out, but using port 8080, I obtain the proper answer. If I remove the application on port 80 and tells `greenlock-express` to use port 80, things work as expected.
Author

Note: it's possible that 80 is the only option available for the plain-port. In this case the documentation should say so :)

Note: it's possible that `80` is the only option available for the plain-port. In this case the documentation should say so :)
Owner

Thanks for the report.

Don't use v2 anymore. It dies in about 48 hours.

Here are the docs for v3:
https://git.rootprojects.org/root/greenlock-express.js/src/branch/v3

Caveats:

  • Most of the links are 404s. They're stubs that I haven't filled out yet.
  • It's still in "beta" for the next... two days...

I'm going to include a special serveLocal(app) method for v3 that will take a port, with documentation explaining that it doesn't work with http-01 plugins.

Thanks for the report. Don't use v2 anymore. It dies in about 48 hours. Here are the docs for v3: https://git.rootprojects.org/root/greenlock-express.js/src/branch/v3 Caveats: * Most of the links are 404s. They're stubs that I haven't filled out yet. * It's still in "beta" for the next... two days... I'm going to include a special `serveLocal(app)` method for v3 that will take a port, with documentation explaining that it doesn't work with http-01 plugins.
Owner

Here's the example for plain port usage:

https://git.rootprojects.org/root/greenlock-express.js/src/branch/master/examples/http/server.js#L32

Feel free to PR to enhance the docs. They're getting better, but they're not perfect and your suggestions would be very welcome.

Here's the example for plain port usage: https://git.rootprojects.org/root/greenlock-express.js/src/branch/master/examples/http/server.js#L32 Feel free to PR to enhance the docs. They're getting better, but they're not perfect and your suggestions would be very welcome.
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: root/greenlock-express.js#6
No description provided.