Securing RPC communication with TLS and auto_encrypt doesn't work

[TheManyula]

I've started setting up single-node cluster on version 1.5.3 and I'm currently following the guide to securing RPC communication with TLS. Note, that I have enabled auto_encrypt´ with allow_tls = true. I started up a fresh instance in bootstrap mode with verify_incoming = trueandverify outgoing = true`. So far, so good.

Now, in step 2, I need to change the settings to verify_incoming = false and add verify_incoming_rpc = true so I can access the UI. Once I do that and restart the instance, I'm getting ==> if auto_encrypt.allow_tls is turned on, TLS must be configured in order to work properly.

What else can I do to make this work?

[hanshasselberg]

@thevanitas you are correct, thats an issue right now (#6338). You can use a consul client to serve the UI until it is fixed.

[stale]

Hey there,
We wanted to check in on this request since it has been inactive for at least 60 days.
If you think this is still an important issue in the latest version of Consul
or its documentation please reply with a comment here which will cause it to stay open for investigation.
If there is still no activity on this issue for 30 more days, we will go ahead and close it.

Feel free to check out the community forum as well!
Thank you!

[hanshasselberg]

This should work now, which is why I am closing this issues.

[ghost]

Hey there,

This issue has been automatically locked because it is closed and there hasn't been any activity for at least 30 days.

If you are still experiencing problems, or still have questions, feel free to open a new one 👍.