Redirector/responder port is hardcoded and cannot be changed on the command line about acmetool HOT 6 CLOSED

This is more or less intentional. Would changing this be useful to you?

from acmetool.

This bit me - running on a service (webfaction) that allows custom binaries on an unprivileged port and then will proxy port 80 from public to your app. I tried to setup this way but it obviously wouldn't work as i can't bind port 80 on the shared host...

Bit of an edge case, but in general there are many good reasons to want to run something behind another reverse proxy or load balancer so setting port is useful.

from acmetool.

You can use port 4402 instead of 402, it will try to bind to both. But sure.

from acmetool.

In my case webfaction issues you with a port to prevent collision with other users...

from acmetool.

Aah. Okay.

from acmetool.

You can now specify additional ports to listen on in a target file (including the default target file):

request:
  challenge:
    http-ports:
      - 1234
      - 127.0.0.1:4567

As part of acmetool's "try anything which could possibly work" philosophy, it will still try to listen on 80/402/4402. Failure to do so is, of course, nonfatal.

from acmetool.