1 of 1 people found this helpful
I had this issue - I had to update my host file on the core to point the public hostname of the CSA to its internal IP address. After I did that - the issues cleared up.
Thank you for your hint. I found that unfortenately CORE server keep an older settings in the cache memory. It helped to restart our production core(restart CSA server, reenroll internal CSA certs didnt helped) and this problem was done.