Thank you for sharing the output. With the additional information, we can now clearly pinpoint why this is happening.
Served certificate in your region → AQDeWGl5wqChykiPKmzj2px0mDf3XRja3wuxfuWgQF0mwQASzqYAGMFagAAAAEJUZWFtU3BlYWsgU3lzdGVtcyBHbWJIAACkRtDPJiIeOU4pehGjg5/fh5rTuB+9xYv5E/1GakyxrAEYO5RfGGLi9nRzM3NlcnZpY2VzLnRlYW1zcGVhay5jb20A Served by Cloudflare in my region → AQDeWGl5wqChykiPKmzj2px0mDf3XRja3wuxfuWgQF0mwQASzqYAGMFagAAAAEJUZWFtU3BlYWsgU3lzdGVtcyBHbWJIAAAmmas0F6CUopziM/yiVh1i+qTZJgXOJuuiFuVfI5y+8AEYZxXfGI8FgnRzM3NlcnZpY2VzLnRlYW1zcGVhay5jb20A Next in line (actual bucket file) → AQDeWGl5wqChykiPKmzj2px0mDf3XRja3wuxfuWgQF0mwQASzqYAGMFagAAAAEJUZWFtU3BlYWsgU3lzdGVtcyBHbWJIAABMNS0e0r2A+84B6zUOqRuUX+P67j0n7zZuZdM1V5PORQEYcaHfGJjcL3RzM3NlcnZpY2VzLnRlYW1zcGVhay5jb20A
The certificate used in my region (Germany) is still valid until January, but unfortunately your certificate has already expired. I don’t know why Cloudflare is still serving such an outdated cache in parts of the US. Unfortunately, there is not much we can do besides purging the cache and hoping Cloudflare updates it soon. This may take a while, especially for requests via HTTPS.
I will kick our IT department so they will click the button rapidly and with authority.
Again, thank you for your assistance!
Thank you, Hubert. At least you’ve been able to identify the issue.
I’ll keep an eye on things. Any idea on what “a while” is with Cloudflare? A couple days, a week, a month? Never been a fan of them. Glad I am working with you guys and not the Cloudflare guys…
It should update the cache rather fast, talking about minutes after purging. Since this only occurs in specific regions, it may take up to 24 hours or a few days.
However, this is an estimate, as Cloudflare’s internal processes aren’t fully visible to us.
The chat is functioning well. I’m unsure how to check which version I’m using, but I pay a monthly fee for TeamSpeak 6 through their service. I’m currently researching how to find the server log, but I suspect that this information can only be accessed from the server side.
Perhaps if the client receives an out of date revocation list have the client try again but add a dynamic parameter to prevent Cloudflare caching, maybe just the date something like that the server ignores, or perhaps if a reqDate parameter is received the server’s response includes a max cache time of 24 hours (not that Cloudflare is respecting that anyway). I know one of the projects I was working on clients on a network that had caching enabled on were having issues and the only thing we could find that prevented that when we can’t control that cache server was to modify the request enough that the cache server saw the request as unique.