Run the upgrade2.x
Do the steps in Before you upgrade first, and Move off rclone if 1.x used an rclone sidecar.
- Start 2.x with
./config-2.0:/configandTZset to the zone 1.x ran in (see the compose file). The import runs on first start; the UI shows progress and the full report. Until it is done the container showsstarting; see Health check. - Sign in with your 1.x admin login.
- If the container name or port changed, update the SABnzbd download client in each Arr. 1.x served on port 8080; 2.x uses 3000. The API key stays the same.
- If 1.x used rclone, run the checks after the first start.
Do not run both
Section titled “Do not run both”Do not run 1.x and 2.x at the same time. Both would use your provider connections.
Roll back
Section titled “Roll back”Stop 2.x and start 1.x on the original ./config. Anything imported or added while on 2.x is not carried back.
What does not carry over
Section titled “What does not carry over”Settings for features 2.x does not have yet are listed in the import report; see What’s new in 2.x. The rclone settings (RC notifications, cache flags) are dropped; the built-in mount does not need them.