This article explains and provides resolution for configuration change scenarios that can affect FogBugz/Manuscript On-Premises in such a way that it stops the mail messaging service.
Environment / Affected versions
- FogBugz on-prems
- Manuscript on-prems
- FogBugz for your Server
The following configuration changes can result in emails not being sent/stuck in the queue.
Rewrite Rule in IIS
When you request for a secure site only, many system admins rely on the IIS rewrite (traditional) rule to accomplish this.
If this is done incorrectly, it could lead to IIS to stop serving for the heartbeat callback (
/821014000/multiheartbeat.asp) and fail (Error 500).
To correct this situation:
- Remove all rewrite rules from FogBugz site.
- Implement the redirection by following the instructions on the Configuring FogBugz On Site to Use HTTPS article.
Incorrect Binding in IIS
There are cases when you want to use multiple instances. To enable this, binding http to an IP or specific domain removing the * can result in stuck emails because the system stops listening on localhost.
Restoring the binding on http to * will correct the issue.