Hi Douglas,

Thank you for posting. We're aware of this issue and are working hard to resolve it. Unfortunately, despite our many efforts, we have been unable to replicate the behavior. At this time, we are working to gather diagnostics on the affected servers so we can pinpoint a cause. (We appreciate all of those who are assisting in this review!) In the meantime, we have created the following knowledge base article to help affected customers overcome the problem. 

If anyone happens to experience this 500 error upon upgrade, you can use the article below to resolve it. That said, we would really appreciate if you still submit a support ticket so we can continue our diagnostics of your environment.

Kind regards,

Hi Douglas,

I wanted to add an update here that the release of Build 8755 addresses the issue with the IIS portion of the installation. We should no longer see this 500 error occurring after upgrade. 

Kind regards,

I have just upgraded to v8762 and have the 500 error. If I show detailed errors then its:

I've checked the ARR settings and all look to be setup correctly, so I'm not sure what the issue is?

It looks like you need to add the following to every domain where you want the domain specific webmail:

Add the following:

- HTTP_X_FORWARDED_FOR

- HTTP_X_FORWARDED_HOST

- HTTP_X_FORWARDED_PREFIX

- HTTP_X_FORWARDED_PROTO

Which is not ideal, luckily I don't have hundreds to do.

Hello YS Tech,

I'm sorry to hear that you encountered this problem on your upgrade. I'm going to start a support ticket with you so we can evaluate this further. 

Kind regards,

Just a favor, would you guys consider "pinning" this thread (or something similar) along with any other caveats on the newest build?  Not forever obviously.  But I found the KB Andrea provided after lots of searching.

Andrea, I set up a main domain and then bound all the other webmails domains to that domain, so I only had to add HTTP_X lines once. So not too bad in the end.

This may have been due to selecting a different installation domain this time as a pose to the default website that I've always set it to. I might not have had the issue if I had just updated as I have previously. The only reason I did that was because of your notes that said this version needed a fully qualified domain, etc. to setup correctly.

Anyway all sorted now.