I have a greenlock server that is sometimes run in port forwarded environments (like Xfinity) where the port forward works from the WAN side, but not the LAN side (they bind the admin interface of the router to WAN interface having the public IP, even though it doesn't need to be). The dry run therefore fails from the LAN side where greenlock resides. I am trying to do skipDryRun in the greenlock config in a way that passes down to ACME.js. The solution of adding an /etc/hosts file entry for each domain doesn't work because the domains are dynamically added, and I am looking for a simpler solution. The greenlock server is not the main server, so all calls to it are explicit, so skipDryRun isn't as needed. It is just handling the generation of certificates for shared mount with nginx.
I tried adding skipDryRun greenlock-express config, and that didn't seem to pass down. I added a config.json where the default one gets created, with skipDryRun in it, but on startup, the defaults overwrite that file. I don't see where to change the defaults with configuration. There is so much modularity and automatic config in the code that is a bit difficult to follow the whole chain.
Thank you for authoring greenlock.
I have a greenlock server that is sometimes run in port forwarded environments (like Xfinity) where the port forward works from the WAN side, but not the LAN side (they bind the admin interface of the router to WAN interface having the public IP, even though it doesn't need to be). The dry run therefore fails from the LAN side where greenlock resides. I am trying to do skipDryRun in the greenlock config in a way that passes down to ACME.js. The solution of adding an /etc/hosts file entry for each domain doesn't work because the domains are dynamically added, and I am looking for a simpler solution. The greenlock server is not the main server, so all calls to it are explicit, so skipDryRun isn't as needed. It is just handling the generation of certificates for shared mount with nginx.
I tried adding skipDryRun greenlock-express config, and that didn't seem to pass down. I added a config.json where the default one gets created, with skipDryRun in it, but on startup, the defaults overwrite that file. I don't see where to change the defaults with configuration. There is so much modularity and automatic config in the code that is a bit difficult to follow the whole chain.
Thank you,
Ben