Is a TLS certificate required in combination with nginx?

[TimmBmn]

I have copyparty running as a systemd service and make it make it accessible to the web through nginx.

When starting/restarting the service i always have these lines in my logs:

could not create TLS certificates: [Errno 2] No such file or directory: 'cfssl'
install cfssl if you want to fix this; https://github.com/cloudflare/cfssl/releases/latest  (cfssl, cfssljson, cfssl-certinfo)
using default TLS certificate; https will be insecure: /var/lib/copyparty/.config/copyparty/cert.pem

Is this relevant for me?
Can i just ignore that the default certificate is insecure because all of the traffic is running through the nginx TLS certificate?

I also found the --no-crt flag which resolves the first warning and the --cert <PATH> flag which lets you point to your own certs and resolves the second warning. The reason i am not just using the --cert flag is, that it doesn't really work for me. My certificate and private key get generated by certbot and live in two separate files, but copyparty expects them to be in the same file.

Any help is appreciated :)

[9001]

no, you can ignore that - it is recommended to handle https in the reverse-proxy and speak plaintext to copyparty, but it will still try to create a cert regardless. And yes, since you know you won't need it, you can use global-option no-crt to opt out; there's no reason to give copyparty a cert in your usecase.

[TimmBmn]

Okay thank you very much for your answer and your awesome work :)