Facing this issue while using authentication with TLS

I followed all the steps mentioned in https://pulsar.apache.org/docs/en/security-tls-transport/ and https://pulsar.apache.org/docs/en/security-tls-authentication/ to use authentication using TLS but somehow whenever I make config changes and restart, broker containers get excited. while trying to look into the logs, I see following errors:

1. org.apache.pulsar.common.util.FileModifiedTimeUpdater - Unable to fetch lastModified time for file ca.cert.pem:
java.nio.file.NoSuchFileException: /ca.cert.pem (address is correct but facing this error for all 3 certificates)

2. org.apache.pulsar.common.util.SslContextAutoRefreshBuilder - Execption while trying to refresh ssl Context Certificate loading error
java.security.KeyManagementException: Certificate loading error

3. Will not attempt to authenticate using SASL (unknown error)

4. ERROR org.apache.pulsar.broker.PulsarService - java.lang.NullPointerException

I was expecting this to run fine but couldn,t find any solution on internet. If you could help me with what could be the issue, it'll be really helpful. I have generated certificate from openSSL as mentioned in the documentation for apache pulsar.

Start by comparing the broker configuration with the TLS transport and TLS authentication documentation linked in the issue, then verify that ca.cert.pem and the other certificate paths exist inside the broker containers. Review the FileModifiedTimeUpdater, SslContextAutoRefreshBuilder, SASL, and PulsarService errors together. Done means the broker restarts without certificate-loading or NullPointerException errors and authentication succeeds.

Written by the indexing model from the issue text.