reading config file /etc/logrotate
acquired lock on state file /data/etc/logrotate.statusReading state from file: /data/etc/logrotate.status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Handling 1 logs
rotating pattern: /data/nginx/*.log after 1 days (3 rotations)
empty log files are not rotated, old logs are removed
considering log /data/nginx/access.log
Now: 2024-10-11 16:07
Last rotated at 2024-10-11 15:00
log does not need rotating (log has been rotated at 2024-10-11 15:00, which is less than a day ago)
considering log /data/nginx/stream.log
Now: 2024-10-11 16:07
Last rotated at 2024-10-11 15:00
log does not need rotating (log has been rotated at 2024-10-11 15:00, which is less than a day ago)
not running postrotate script, since no logs were rotated
[11-Oct-2024 16:07:54] NOTICE: fpm is running, pid 524
[11-Oct-2024 16:07:54] NOTICE: ready to handle connections
[Global ] › ℹ info Using Sqlite: /data/etc/npm/database.sqlite
[Migrate ] › ℹ info Current database version: none
[IP Ranges] › ℹ info Fetching IP Ranges from online services...
[IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[SSL ] › ℹ info Certbot Renewal Timer initialized
[IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[Global ] › ℹ info Backend PID 529 listening on port 48693 ...
[Nginx ] › ℹ info Starting Nginx
2024/10/11 16:07:56 [notice] 548#548: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/7/0)
[SSL ] › ℹ info Requesting Certbot certificates for Cert #1: clawsucht.drayddns.com
[SSL ] › ℹ info Command: certbot --logs-dir /tmp/certbot-log --work-dir /tmp/certbot-work --config-dir /data/tls/certbot certonly --config "/data/tls/certbot/config.ini" --cert-name "npm-1" --authenticator webroot --preferred-challenges "http,dns" --domains "clawsucht.drayddns.com" --email "shedowe@clawsucht.de"
[SSL ] › ✔ success Account registered.
Requesting a certificate for clawsucht.drayddns.com
Successfully received certificate.
Certificate is saved at: /data/tls/certbot/live/npm-1/fullchain.pem
Key is saved at: /data/tls/certbot/live/npm-1/privkey.pem
This certificate expires on 2025-01-09.
These files will be updated when the certificate renews.
NEXT STEPS:
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
nginx: [emerg] BIO_new_file("/data/tls/certbot/live/npm-1.der") failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/data/tls/certbot/live/npm-1.der, rb) error:10000080:BIO routines::no such file)
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed
[Nginx ] › ℹ info Reloading Nginx
[Nginx ] › ℹ info Reloading Nginx
[Nginx ] › ℹ info Reloading Nginx
[Nginx ] › ℹ info Reloading Nginx
2024/10/11 16:10:53 [error] 3216#3216: *66 quic getsockopt(SO_COOKIE) failed (92: Protocol not available) while creating quic connection, client: 89.247.58.115, server: 0.0.0.0:443
2024/10/11 16:10:53 [error] 3216#3216: *66 quic bpf failed to generate socket key while creating quic connection, client: 89.247.58.115, server: 0.0.0.0:443
2024/10/11 16:10:53 [error] 3216#3216: *66 quic getsockopt(SO_COOKIE) failed (92: Protocol not available) while handling frames, client: 89.247.58.115, server: 0.0.0.0:443
2024/10/11 16:10:53 [error] 3216#3216: *66 quic bpf failed to generate socket key while handling frames, client: 89.247.58.115, server: 0.0.0.0:443
[Nginx ] › ℹ info Reloading Nginx