Can you tell us who prepared this Docker image?
Were you able to isolate the elements related to your technical environment (firewall, Azure hosting, IIS server, etc.)? To make sure that this is not what is blocking?
I suggest you install a test instance on a LAMP environment via Composer and check if you get the same error message. It is essential to make sure that the blocking point is on the Mautic side and not on your environment side.
Thank you for your reply. I’m using the last available version of docker-mautic.
I’ve finally figured out the problem. I was implementing the solution from the link I’ve sent, but, instead of adding a new AssertionConsumerService with the local url of the reverse proxy, I should have added the public url, as, by default, it seems that the location was set with the reverse proxy url.