Webserver Error 500 - CloudPanel-3.2.0319
We did a new installation on a Win2019 Server with SQL 2017. (everything like described in the installation manual)
We already have an older installation where we had no problems with installing. At first we also migrated the DB first to the new server and checked the box, that the scripts don't run. (I did not find a config.xml file like described above the "Skip database configuration" Button, but a settings.xml which looks OK)
After that we only get an error 500 in IIS and can't even get the login page.
So I uninstalled it again, removed the database and did just a fresh install with creating the Database and everything. We still just get the error 500 and no other hint, what is wrong.
Any help would be appreciated, so we can migrate it to this new server.
P.S. We also upgraded the version on the old server to 3.2.0319, but it shows version 3.2.318 in the "Setup Cloudpanel" after the upgrade. I think that's just a typo.
After you installed, did you configure the settings first by going to https://localhost/cloudpanel/admin/setup ?
I tried, but I get the same webserver error 500 also for: https://localhost/cloudpanel/admin/setup
You replied to another post with the same error 500, that you did a remote session and reinstalled IIS with "lesser" options. I tried that as well, and selected only the defaults. (I see that we have a lot more installed on the old server) but it still does not change anything.
@comelfex Can you post the screenshot of the error message? If you access it from the server using localhost it should show the full error message
Here you go. But not really more informations.
@comelfex That isn't the application throwing an error. That looks like the application pool can't start. Can you check the IIS application pools and see if the CloudPanel one is stopped?
Was there a resolution for this? Same problem moving to a new server. TIA
@techsupport usually reinstalling IIS and CloudPanel fixes it. We are thinking .NET 4.7 is installed after IIS and causes it to not register in IIS. You can try manually registering it to see if that fixes it
Reinstall did the trick but I swear I didn't pick different options. Just the defaults. The only difference is looks like the first IIS install was missing the 2 v4.5 .NET Apps in the Pool.