Optional
account2048
Optional
accountThe name the ACME account RSA private key is stored in the keychain with
'auto-tls-acme-account-private-key'
Optional
acmeWhich ACME service to use - examples are:
'https://acme-v02.api.letsencrypt.org/directory'
Optional
autoAny mapped addresses are added to the observed address list. These
addresses require additional verification by the @libp2p/autonat
protocol
or similar before they are trusted.
To skip this verification and trust them immediately pass true
here
false
Optional
certificateThe key the certificate is stored in the datastore under
'/libp2p/auto-tls/certificate'
Optional
certificateHow many bits the RSA private key for the certificate should be
2048
Optional
certificateThe name the certificate RSA private key is stored in the keychain with
'auto-tls-certificate-private-key'
Optional
forgeThe top level domain under which we will request certificate for
'libp2p.direct'
Optional
forgeWhere to send requests to answer an ACME DNS challenge on our behalf - note
that /v1/_acme-challenge
will be added to the end of the URL
'https://registration.libp2p.direct'
Optional
provisionCertificates are acquired when the self:peer:update
event fires, which
happens when the node's addresses change. To avoid starting to map ports
while multiple addresses are being added, the mapping function is debounced
by this number of ms
5000
Optional
provisionHow long asking the forge endpoint to answer a DNS challenge can take before we retry
60_000
Optional
provisionHow long to attempt to acquire a certificate before timing out in ms
120_000
Optional
renewHow long before the expiry of the certificate to renew it in ms, defaults to one day
86_400_000
How many bits the RSA private key for the account should be