Document: error when testing with ngrok pro without having created a CNAME
If you are setting up ngrok to enable remote access to your Site.js site/app for testing and you forget to set up a CNAME to point to your ngrok subdomain, you will see errors similar to the following in the console:
[acme-v2] handled(?) rejection as errback: Error: [acme-v2] (E_STATE_INVALID) challenge state for 'pi.ar.al': 'invalid' at /email@example.com/acme-v2/node.js:422:29 at process._tickCallback (internal/process/next_tick.js:68:7)
This should be documented. It’s niche but it might bite someone else.