We are in the process to migrate our cloudpanel installation from Windows Server 2012 r2 to Windows Server 2022.
We’re currently using a locally installed SQL 2016 instance for cloudpanel.
For the new server we will also install a local SQL 2019 instance for cloud panel to use.
Is the following process still accurate?:
- Install IIS on the new server and SQL on the server you want to move the database to
- Backup and restore the current CloudPanel database to the new server
- Install CloudPanel on the new server (make sure it is the same version) but choose the “Skip database configuration” checkbox as seen here: https://kb.knowmoreit.com/docs/install-cloudpanel/install-cloudpanel/
- Copy the branding folder and documentation folder from the old server as mentioned in that article
- Edit the settings.xml file in the Config directory and change the SQL connection string to point to the new database
Would this be the correct procedure, or would you recommend a different approach?
Thanks
Jacob Dixon 2023-11-13 08:52
@rechenzentrumkraemer-it-de That is correct. The reason for checking that checkbox is because by default CloudPanel tries to setup a new SQL database during the install and this will tell it to skip that process. The settings.xml file contains the SQL connection string which is what you modify to point it to the new SQL server.
If you would like, we would be more than happy to jump on a remote session and do it for you. We could schedule a time that works.
Jacob Dixon 2023-11-13 09:19
@rechenzentrumkraemer-it-de I went ahead and put more detailed instructions here: https://kb.knowmoreit.io/en/migrations
We just moved to a new server per these instructions and every 21 minutes we’re getting an ASP.NET error as below. No one is one the console and no process known to us is requesting localhost/CloudPanel
| DBxx | 1309 | Warning | ASP.NET 4.0.30319.0 | Application | 11/13/2023 5:52:37 PM |
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 11/13/2023 5:52:37 PM Event time (UTC): 11/13/2023 11:52:37 PM Event ID: febccc26609344f9ab3471a0ef82cc70 Event sequence: 4 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/CloudPanel-1-133443931494321781 Trust level: Full Application Virtual Path: /CloudPanel Application Path: C:\Program Files (x86)\Know More IT\CloudPanel\ Machine name: DBXX Process information: Process ID: 8492 Process name: w3wp.exe Account name: XXX\TooMuch Exception information: Exception type: COMException Exception message: The request is not supported. (Exception from HRESULT: 0x80070032)
Request information: Request URL: http://localhost/CloudPanel/ Request path: /CloudPanel/ User host address: 127.0.0.1 User: Is authenticated: False Authentication Type: Thread account name: XXX\TooMuch Thread information: Thread ID: 7 Thread account name: XXX\TooMuch Is impersonating: False Stack trace:
Custom event details:
Jacob Dixon 2023-11-13 19:13
@techsupport do you have port 443 ssl configured and do you have any bindings in IIS? Your error states the request hit port 80 http
Jacob Dixon 2023-11-13 19:34
@techsupport I assume this is how it was before? CloudPanel does not perform any COM interop ls in code, so it could be a third party library.
Do you happen to see any TokenMissing warnings or errors in the CloudPanel log files?
TechSupport 2023-11-14 08:30
The proxy is new. There are no errors in the CP logs… the timing matches up with your license checks though. Looks like every 20 minutes
Jacob Dixon 2023-11-14 08:32
@techsupport the license checks are not every 20 minutes but they are when the application starts. Can you check the idle time on the IIS application pool and see if its set to 20? If so, please change to 0 and see if that helps
TechSupport 2023-11-14 12:06
Thanks. The application idle timeout was set to 20 minutes. Changed to 0
