This message was deleted.

@Zixuan Liu I’m following the apache docs and your blogpost, any ideas?

could you try bin/pulsar standalone -nfw

That works (I can connect and authenticate with a Java client)

Could you try Pulsar 3.0.1?

I just tried it with Pulsar 3.1.0 and I get the same error as before

See this log:

2023-08-15T15:23:26,736+0200 [main] INFO  org.apache.pulsar.functions.worker.WorkerUtils - Create Pulsar Admin to service url <http://localhost:8080>: authPlugin = org.apache.pulsar.client.impl.auth.AuthenticationTls, authParams = {"tlsCertFile":"/Users/alex/Desktop/pulsar/apache-pulsar-3.0.0-tls/conf/tls-certs/client.cert.pem","tlsKeyFile":"/Users/alex/Desktop/pulsar/apache-pulsar-3.0.0-tls/conf/tls-certs/client.key-pk8.pem"}, tlsTrustCerts = /Users/alex/Desktop/pulsar/apache-pulsar-3.0.0-tls/conf/tls-certs/ca.cert.pem, allowTlsInsecureConnection = false, enableTlsHostnameVerification = false

service url is incorrect, it should be http://localhost:8081. Could you add

tlsEnabled=true

to

conf/standalone.conf

? And then I think the Pulsar works fine.

Yes, I saw it too. I’m wondering why the function worker tries to connect to a different serviceurl, I think that’s a bug

I check the Pulsar codebase, I think

tlsEnabled=true

should be works fine. I will fix this bug.

Thank you 🙂

I made a PR to fix this issue: https://github.com/apache/pulsar/pull/21013, could you review and verify this PR?

I had a look and to me the code is looking good but I’m not a committer, so someone else will have to give it a final check

I'm also having tls issues with cert-manager. Not sure if we can troubleshoot my issues 🙂

Same issue? If so, I think my PR can fix your issue! But my PR breaks some tests, I need time to fix that.

Not same issue. I'm trying to configure tls using cert-manager and they aren't generated as .pem files but like so in pulsar-tls secret. ca.crt: 1168 bytes tls.crt: 1549 bytes tls.key: 1675 bytes

Could you create a issue in the Pulsar repo？