Matthias Werning

Having the same issue as well. Creating an own helm chart should work, but seeing this in the official version would be great.

Can confirm that this also happens on our system. The intermediate certificate in the tls.crt chain of the leaf certificate is still the old one. In our case the intermediate...

Bumping this, as I ran into this problem right now as well. As far as I examined the standard golang reverse proxy lib, there is a handler for WebSocket upgrades...

Okay, just made an own proxy middleware copying the current implementation minus the extra raw handler for websockets. Works for secure WebSockets. Didn't test it for unencrypted connections though.

@aldas Sorry for responding late, I was a bit busy the recent days. I'm already creating a PR right now. However, for a unit test, that would require a server...

You should know that every error that is occurring in an AMQP connection will force the connection to be closed. Thus it is normal, that the robust connection will try...

Any update to this? Would also require the fix to be available for both major versions. Thanks.

I could also create a pull request with the solution I proposed if this approach would be ok.

Update: I think I messed a few things up here and the error doesn't occur as described. As @Darsstar already mentioned there should be no issue on initial connect except...

One more thing to clarify: The token is currently updated in an async loop in a certain interval that will always ensure that a fresh token is available. This is...