This isn't an issue with NGINX, it's an issue with your configuration.
From the output of the journal for your NGINX runs:
dez 02 21:48:16 walter-ubuntu nginx[2210]: 2024/12/02 21:48:16 [emerg]
2210#2210: cannot load certificate
"/home/walter/zapstart/MultiPro02/backend/certs/cert.pem":
BIO_new_file() failed (SSL: error:80000002:system library::No such file
or directory:calling
fopen(/home/walter/zapstart/MultiPro02/backend/certs/cert.pem, r)
error:10000080:BIO routines::no such file)
Somewhere in your configuration in NGINX, you were referring to a path
called "/home/walter/zapstart/MultiPro02/backend/certs/cert.pem" which
is **no longer existing**.
You will need to either revise your configuration to remove this path
and replace it with another one, or you need to figure out where these
certificates went. Either way, NGINX is being told to read certificates
at a path that doesn't exist on your system.
Marking as "Invalid" as this is a configuration-specific issue on your
environment and not a bug in the package.
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090886
Title:
package nginx 1.24.0-2ubuntu7.1 failed to install/upgrade: o
subprocesso instalado, do pacote nginx, o script post-installation
retornou erro do status de saída 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2090886/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
