At line 1 changed one line |
CrushFTP 6 is a separate install, and requires a CrushFTP 6 license code. Prior CrushFTP versions require purchasing an upgrade code to use in CrushFTP 6. [http://www.crushftp.com/pricing.html]. Download a fresh copy of CrushFTP 6. [http://www.crushftp.com/download.html] |
CrushFTP 11 is a separate install, and requires a CrushFTP 11 license code. Prior CrushFTP versions require purchasing an upgrade code to use in CrushFTP 11. [http://www.crushftp.com/pricing.html]. Download a fresh copy of CrushFTP 11 and extract it to a safe location. [http://www.crushftp.com/download.html] |
At line 4 added one line |
Video covering the upgrade process: [https://youtu.be/k9BANsDsDZM] |
At line 5 changed one line |
!1.) Run your prior CrushFTP version, and uninstall the daemon or service if its installed. |
!CrushFTP 6/7/8/9/10 Upgrade to CrushFTP 11: |
At line 7 changed one line |
2.) Copy over your users folder, and prefs.xml file from the old version to the new version's folder. |
1.) Register your CrushFTP 11 license key within your current version in the admin dashboard, about tab.\\ |
At line 9 changed one line |
! *Do not replace your WebInterface folder, the CrushFTP 6 WebInterface folder is very different, and replacing it with the older folder would break CrushFTP 6. |
2.) Copy over your users folder, prefs.xml, ssh private keys, and ssl keystores files from the old version to the new version's folder (see Critical Post Update Items below).\\ |
At line 11 changed one line |
3.) Run CrushFTP 6. |
''Do not replace your WebInterface folder, the CrushFTP 11 WebInterface folder is very different, and replacing it with the older folder would break CrushFTP 11.''\\ |
At line 13 changed one line |
[attachments|gui_setup.png] |
3.) Check on Services.msc under what exact OS user is the CrushFTP service running.\\ |
At line 15 changed one line |
4.) Click Create New Admin User. Create your own admin user that will be used for managing the server. |
4.) Run CrushFTP 6/7/8/9/10 and click 'Remove Daemon / Service'. Alternatively you can run CrushFTP v11 and use its button to remove the service too.\\ |
At line 17 changed one line |
5.) Click "Start Temporary Server". The server will now be running and ready for use as long as you keep this window open. |
5.) Make sure you have the "Java" folder in the CrushFTP v11 folder. OpenJDK17+ is recommended. Follow the readme.txt file in the CrushFTP folder.\\ |
At line 19 changed one line |
6.) Login using the web browser to your server using the admin user you just created. Click the 'Admin' button. |
6.) Run CrushFTP v11.\\ |
At line 21 changed one line |
7.) Go to Preferences, and click on each server item. Verify to the right that each port (FTP,HTTP,SFTP) is set to use users from the correct User Connection Group. (Probably "MainUsers" or "lookup_21".) |
7.) Click "Start Temporary Server". The server will now be running and ready for use as long as you keep this window open.\\ |
[attachments|gui_setup.png]\\ |
At line 23 changed one line |
[attachments|user_connection_group.png] |
8.) Login using the web browser to your server using your normal 'crushadmin' user. Go to the Admin, About tab and enter in your CrushFTP 11 license code if not registered on your prior CrushFTP version, from previous steps.\\ |
At line 25 changed one line |
8.) Open the user manager, select the Convert All Users from the convert menu. (If you were already using CrushFTP 5.5 and above, this can be skipped.) |
9.) Go back to the GUI window, and click 'Install Daemon / Service'\\ |
At line 27 changed one line |
[attachments|convert_users.png] |
10.) Go to the services.msc and set the same user as you had on your prior CrushFTP 6/7/8/9/10 version, to run the CrushFTP 11 service. Restart the service for the changes to apply. |
At line 29 changed one line |
9.) Test and verify things are working on the new server. If necessary, you can add or remove server groups in the [IP Servers] of the server prefs. |
11.) Update any paths in the admin, Preferences for SSH keys or SSL keystores to point to your new CrushFTP 11 folder. |
At line 31 removed 3 lines |
10.) Install the daemon / service again using the main CrushFTP application. |
|
|
At line 36 changed one line |
!!Followup items:\\ |
!!v6/v7/v8/v9/v10 to v11 Followup items:\\ |
At line 41 changed one line |
Copy over any custom logo images from your WebInterface folder, but do not overwrite any login.html files as CrushFTP 6 is different.\\ |
Copy over any custom logo images from your WebInterface folder, but do not overwrite any login.html files as CrushFTP 11 is different.\\ |
At line 46 changed 2 lines |
''On OS X, these are in the app bundle. CrushFTP5.app/Contents/Resources/Java/''\\ |
''On CrushFTP4, you only had a DSA key located in the "conf" folder. CrushFTP4.app/Contents/Resources/Java/conf/'' |
\\ |
Copy over your Jobs folder if you have the enterprise version. Its in your CrushFTP folder.\\ |
\\ |
Loading DB drivers that are not in your classpath has also changed. This means if your DB drivers |
are not part of your plugins/lib folder, they will not be loaded by CrushFTP. (Statistics DB if you changed it, SQL Users if you are using that, etc.) |
\\ |
If you want your statistics for reporting to transfer over from v6/v7/v8/v9/v10 to v11, then copy the statsDB folder too.\\ |
\\ |
If and __only if__ the SHA3 password hashing policy was enabled on the old version, and the users cannot log in after the upgrade, edit the main server configuration file prefs.XML locate the <sha3_keccak> key, change it's value from __false__ to __true__\\ |
At line 50 changed one line |
!!CrushFTP4 upgrade troubleshooting tips. |
---- |
!Linux Upgrade:\\ |
At line 59 added one line |
- download the crush package, unzip it into /var/opt \\ |
At line 53 changed one line |
v4 has a bit of a mess on its user connection groups. So when you look in the folder "users" you see MainUsers, lookup_21, lookup_80, etc. |
- make it executable, as root : chmod +x crushftp_init.sh \\ |
At line 55 changed one line |
Figure out which ones are correct. MainUsers is the default location since v5. But you can use the other named folders just fine too. |
- register your CrushFTP 11 license key in your old CrushFTP admin dashboard, about tab\\ |
At line 57 changed one line |
In the prefs, on the tab with the list of ports, down at the bottom is a list of the user connection groups. Remove or add them as appropriate to match up with the real ones you have based on the folder names in the users folder. |
- copy over the files from the above steps for the Windows / macOS upgrade\\ |
At line 59 changed one line |
Then on each port, check to see what user connection group they are configured for. Assign them appropriately. |
- change dir into /var/opt/CrushFTP11/ \\ |
At line 61 changed one line |
If you haven't done this then login may fail when you start using CrushFTP6 as it can't find the users since they aren't associated to the port you are using. |
- while as root, execute: ./crushftp_init.sh uninstall -- for all older versions daemon launch reference to be removed. (No CrushFTP app files are touched)\\ |
|
- while as root, execute: ./crushftp_init.sh install -- to have latest CrushFTP installed daemon launch reference added. (No CrushFTP app files are touched)\\ |
|
---- |
|
!!Critical Post Update Items:\\ |
Copy over your TempAccounts folder if you have been using the WebInterface 'Share...' feature.\\ |
\\ |
Copy over your "s3" folder which has all the XML pointers to your S3Crush filesystem...only applies if you use S3Crush\\ |
\\ |
Copy over your Previews folder so image previews don't need to be re-generated.\\ |
\\ |
Copy over any custom logo images from your WebInterface folder, but do not overwrite any login.html files as CrushFTP 11 is different.\\ |
\\ |
Copy over your SSL keystore if you had it in your CrushFTP folder, and update the Preferences, encryption, SSL config to point at the new location.\\ |
\\ |
Copy over your 'jobs" folder if you have the enterprise version. It is in your CrushFTP folder.\\ |
\\ |
Your daemon/service may have been running with additional memory, re-configure the new version with the equivalent memory.\\ |
\\ |
Your daemon/service may have been running as a domain user on Windows. Change the service to be running as that domain user again or UNC VFS paths will fail.\\ |
\\ |
Copy over your private SSH key files for the server if they are in their default location. (ssh_host_rsa_key, ssh_host_rsa_key.pub, ssh_host_dsa_key, ssh_host_dsa_key.pub, etc.)\\ |
\\ |
Optional: If you want your statistics for reporting to transfer over from v6/v7/v8/v9/v10 to v11, then copy the statsDB folder too.\\ |
\\ |