• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 918
  • Last Modified:

SBS 2011/Exchange 2010 - error when accessing webmail from the internet

Hello experts,

I have sbs 2011/exchange 2010 running on a single box. There is a local ssl certificate installed and when I try to access webmail via https://webmail.mydomain.com/exchange I get the following error.

First i get the certrificate error (There is a problem with this website's security certificate) which is ok, when I click on (Continue to this website (not recommended), the below error comes up.

This was working ok before, but this error has started in the last few days. (the certificate error is not the problem, i know this is due to the local certifiacte, but the problem is i dont get the webmail login page)


Server Error in '/' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

Any help will be much appreciated.
1 Solution
Normally you should access it through https://webmail.mydomain.com/owa and not /exchange
Did you configure configure any redirect recently ?
jiveman74Author Commented:
Hi Thanks,

Yes i did a redirection, this may have been the issue. Changed it back to owa and seem to work ok now

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now