I've found the issue and have managed to resolve it. I don't know what caused it yet thought. For completeness I'll post the steps I took and solution that solved it. So after some more investigating, I found out that POST requests never made it to the ReplicationServlet responsible for handling the...

Even when creating a new user, the error is the same.

I see I overlooked this comment earlier. The ReplicationServlet is active and the configuration seems to be correct:

This is test connection log for the failing publisher:Replication test to http://publish01:4503/bin/receive?sling:authRequestLogin=12024-06-19 16:55:29 - Create new HttpClient for Publish Agent2024-06-19 16:55:29 - * Auth User: replication-receiver2024-06-19 16:55:29 - * HTTP Version: 1.12024-06-19 ...

Thanks for you reply. You're right that it's not an error. It's a warning statement and a debug statement that goes into a bit more details about the warning. The replication user is present on the publish instance and also has the correct access. Just as a test I also tried using the admin user and...

Thanks for your reply and the link. Unfortunately, none of the resolutions there worked in my case. The issue is still present.

Good day all,As of this morning our system is experiencing an issue with the default replication to one of the publishers (the other is fine). No code or configuration changes have been made in the last days that could have caused it. The status of the replication agent on the author is "blocked". W...