HEX
Server: Apache/2.4.59 (Debian)
System: Linux keymana 4.19.0-21-cloud-amd64 #1 SMP Debian 4.19.249-2 (2022-06-30) x86_64
User: lijunjie (1003)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: /var/lib/snapd/sequence/certbot.json
{"sequence":[{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5057","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n  - Automatically prove to the Let's Encrypt CA that you control the website\n  - Obtain a browser-trusted certificate and set it up on your web server\n  - Keep track of when your certificate is going to expire, and renew it\n  - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5214","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n  - Automatically prove to the Let's Encrypt CA that you control the website\n  - Obtain a browser-trusted certificate and set it up on your web server\n  - Keep track of when your certificate is going to expire, and renew it\n  - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5234","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n  - Automatically prove to the Let's Encrypt CA that you control the website\n  - Obtain a browser-trusted certificate and set it up on your web server\n  - Keep track of when your certificate is going to expire, and renew it\n  - Help you revoke the certificate if that ever becomes necessary.\n"}],"current":"5234","migrated-hidden":false,"migrated-exposed-home":false}