¶ 
The model backing the ‘CloudPanelContext’ context has changed since the database was created
The model backing the ‘CloudPanelContext’ context has changed since the database was created
The model backing the ‘CloudPanelContext’ context has changed since the database was created. Consider using Code First Migrations to update the database (http://go.microsoft.com/fwlink/?LinkId=238269).
¶ 
Solution
This error message is telling you that your database is not up to date and it needs to be updated. With each upgrade of CloudPanel there may be changes to the database that need to be made.
Each time that CloudPanel is started (the Application Pool in IIS), CloudPanel checks if an update needs to be made to the database. If you receive the this error, try recycling the CloudPanel application pool in IIS. If the error continues, then something is wrong with the database and you must contact support.
¶ The WinRM client sent a request to an HTTP server and received a response stating that the requested HTTP
System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server <> failed with the following error message:
The WinRM client sent a request to an HTTP server and received a response stating that the requested HTTP -The URL was not available. This response is typically returned by an HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.
¶ Solution
This can occur if you have a larger environment and the amount of data CloudPanel needs to retrieve exceeds the default for WinRM.
To adjust this, open regedit.exe and navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client"
Create a DWORD (32-bit) value named maxEnvelopeSize and set the value to 8192 decimal.
¶ The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.
Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.
¶ Solution One
When you apply updates to Microsoft Exchange it will most like reset the Basic Authentication setting on the Powershell virtual directory. You will need to go back into EAC and enable this again.
Warning
Do not enable this IIS. Make sure you do this through ECP
¶ Solution Two
The IIS website CloudPanel is using is not running under an application pool that is running as a domain user that has rights to Microsoft Exchange. Please verify that CloudPanel is running under the correct application pool.
¶ Request failed with status code Unauthorized
You can receive this message for a couple of reasons, depending on if you are access a company in Microsoft 365 or if you are accessing a on-prem customers.
¶ Solution One
If the customer you are accessing is a Microsoft 365 customers, then the access token has expired but the CloudPanel service hasn’t renewed it yet. The most common reason is your CloudPanel Service is not running or may need to be restarted
¶ Solution Two
If you are access an on-prem customer, the account you are using does not have permissions. Please contact the CloudPanel hoster or support@knowmoreit.io