Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- -------------------------------------
- _ ()
- | | ___ _ __
- | | / __| | | / \
- | | \__ \ | | | () |
- |_| |___/ |_| \__/
- Brought to you by linuxserver.io
- We gratefully accept donations at:
- https://www.linuxserver.io/donate/
- -------------------------------------
- GID/UID
- -------------------------------------
- User uid: 99
- User gid: 100
- -------------------------------------
- [cont-init.d] 10-adduser: exited 0.
- [cont-init.d] 20-config: executing...
- [cont-init.d] 20-config: exited 0.
- [cont-init.d] 30-keygen: executing...
- using keys found in /config/keys
- [cont-init.d] 30-keygen: exited 0.
- [cont-init.d] 50-config: executing...
- Variables set:
- PUID=99
- PGID=100
- TZ=America/New_York
- URL=mydomain.com
- SUBDOMAINS=sonarr,nextcloud,server,lidarr
- EXTRA_DOMAINS=
- ONLY_SUBDOMAINS=true
- DHLEVEL=2048
- VALIDATION=dns
- DNSPLUGIN=cloudflare
- EMAIL=email@outlook.com
- STAGING=
- 2048 bit DH parameters present
- SUBDOMAINS entered, processing
- SUBDOMAINS entered, processing
- Only subdomains, no URL in cert
- Sub-domains processed are: -d sonarr.mydomain.com -d nextcloud.mydomain.com -d server.mydomain.com -d lidarr.mydomain.com
- E-mail address entered: email@outlook.com
- dns validation via cloudflare plugin is selected
- Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
- Generating new certificate
- Saving debug log to /var/log/letsencrypt/letsencrypt.log
- Plugins selected: Authenticator dns-cloudflare, Installer None
- Obtaining a new certificate
- Performing the following challenges:
- dns-01 challenge for lidarr.mydomain.com
- dns-01 challenge for nextcloud.mydomain.com
- dns-01 challenge for server.mydomain.com
- dns-01 challenge for sonarr.mydomain.com
- Unsafe permissions on credentials configuration file: /config/dns-conf/cloudflare.ini
- Waiting 10 seconds for DNS changes to propagate
- Waiting 10 seconds for DNS changes to propagate
- Waiting for verification...
- Waiting for verification...
- Cleaning up challenges
- Cleaning up challenges
- IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/sonarr.mydomain.com/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/sonarr.mydomain.com/privkey.pem
- Your cert will expire on 2019-09-27. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot
- again. To non-interactively renew *all* of your certificates, run
- "certbot renew"
- - Your account credentials have been saved in your Certbot
- configuration directory at /etc/letsencrypt. You should make a
- secure backup of this folder now. This configuration directory will
- also contain certificates and private keys obtained by Certbot so
- making regular backups of this folder is ideal.
- - If you like Certbot, please consider supporting our work by:
- Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
- Donating to EFF: https://eff.org/donate-le
- IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/sonarr.mydomain.com/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/sonarr.mydomain.com/privkey.pem
- Your cert will expire on 2019-09-27. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot
- again. To non-interactively renew *all* of your certificates, run
- "certbot renew"
- - Your account credentials have been saved in your Certbot
- configuration directory at /etc/letsencrypt. You should make a
- secure backup of this folder now. This configuration directory will
- also contain certificates and private keys obtained by Certbot so
- making regular backups of this folder is ideal.
- - If you like Certbot, please consider supporting our work by:
- Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
- Donating to EFF: https://eff.org/donate-le
- New certificate generated; starting nginx
- [cont-init.d] 50-config: exited 0.
- [cont-init.d] 99-custom-files: executing...
- [custom-init] no custom files found exiting...
- [cont-init.d] 99-custom-files: exited 0.
- [cont-init.d] done.
- [services.d] starting services
- [services.d] done.
- nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
- nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
- no field package.preload['resty.core']
- no file './resty/core.lua'
- no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
- no file '/usr/local/share/lua/5.1/resty/core.lua'
- no file '/usr/local/share/lua/5.1/resty/core/init.lua'
- no file '/usr/share/lua/5.1/resty/core.lua'
- no file '/usr/share/lua/5.1/resty/core/init.lua'
- no file '/usr/share/lua/common/resty/core.lua'
- no file '/usr/share/lua/common/resty/core/init.lua'
- no file './resty/core.so'
- no file '/usr/local/lib/lua/5.1/resty/core.so'
- no file '/usr/lib/lua/5.1/resty/core.so'
- no file '/usr/local/lib/lua/5.1/loadall.so'
- no file './resty.so'
- no file '/usr/local/lib/lua/5.1/resty.so'
- no file '/usr/lib/lua/5.1/resty.so'
- no file '/usr/local/lib/lua/5.1/loadall.so')
- Server ready
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement