SSL and Wemail

[Nomad]

Good morning. We have an issue and a question regarding ME Enterprise 10.45.

Question:
LE certificates work fine, however we have to Import into Personal Store not Web Hosting Store? Can this be changed or is it hard wired?

Issue:
After every Windows Server 2019 update and restart we cannot access Webmail and Mail Admin via browser. We have to run MEinstaller with elevated perms and select option 2. This works (sometimes have to do 2 times).

We have made sure that the IME account has a secure password (Server requirements) and checked the App pool.. Everything is fine.

Does anyone have a fix or suggestion?

Thanks all.

[Admin]

Currently the certificates for the mail services have to be in the personal store. The web apps of course can be either since they are under IIS.

An update should not affect the web applications - I don't see what configuration it would change to affect them. Do you know what the error is after you restart? The Windows event log should have more details, or even the error page IIS returns. The MEInstaller option 2 does a bit, so the error messages should help narrow it down.

[Nomad]

No errors in event log related to webmail webadmin. We only get IIS service not available - 503.

We actually just restarted the sever manually lseveral times to see if we can recreate scenario.

Yes, after every restart got same error. IIS is running fine (we host many sites that are running), nothing in mmc indicating error or stopped etc.

So I don't think it's windows update related.

[dedicate-it.net]

Something is crashing your IIS Application pool for your webmail site.

Service Unavailable is the error you get 99% of the time when the application pool shuts down.

The reason it is available for a few minutes then dies has to do with "Rapid Fail Recovery" in IIS -- the pool will attempt to restart automatically 5 times within "x" number of minutes -- when it crashes that last time, IIS halts the application pool permanently.

You have a configuration issue or permissions issue somewhere that is causing IIS to fail that application pool.

[Nomad]

Fair enuff and it makes sense. We setup a dummy sever with the default settings for Both Pools. This works fine and we compared the pool settings with the problematic server and they are identical.

That said, I think it may have to do with Password Strength. We changed the min requirements a while back and we believe it began then.

Will test during idle time and ping back.

Thanks for the assist.