Thank you for contacting Sitefinity support.
The problem is caused because Sitefinity is messaging the workflow internally, not from the same location from which you are trying to publish the item. This is why we've introduced the WorkflowBaseUrl setting which allows you to configure where the WorkflowService endpoint should be resolved.
Would it be possible to share whit us some additional information on the specific use case scenario, namely how the site bindings are configured in IIS (you can provide a screenshot if possible), and if you have added references to the host header for this site in the hosts file on the server.
In the meantime, what you can try is referencing the host headers for both bindings in the hosts file, for example:
And remove the WorkflowBaseUrl setting. if any issues persist, please do not hesitate to let us know, we'll be glad to help you further.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items