My domain is: senseering.net
I ran this command:
greenlock get domain
It produced this output:
The api is rate limited for exact domain
This is a similar question like the one here.
We are developing a distributed network where every participant should be able to share and sell data to other participants. Anyone who wants to join the network should be able to get a valid https connection to the centralized marketplace. Our current approach is to create subdomains like device-name.user-name.senseering.net that points to the correct ip address and afterwards let the software on the participants device itself retrieve the certificate via greenlock/lets encrypt.
As stated in the linked thread this will be rate limited heavily until the system is not usable anymore. So we also tried to go with direct ip-address verification, but this did not work with lets encrypt.
Currently i am out of ideas where we can get more then 50 certificates per week without hitting the rate limit and without the participants needing its own domain. Is there a workaround to solve this or is there some way to work together with lets encrypt on a solution?