Cloudron Forum

Hello James, hello nebulon,

Thank you for your explanations and recommendations.

To clarify the reason for our migration scenario: Cloudron 7.3.6 is the version currently installed on the existing destination server in our internship environment. It is a bare-metal server already hosting applications and users.

Our goal is to migrate only the Nextcloud application from the source Cloudron 7.4.1 instance, while preserving all other applications, users and platform settings on the destination.

We understand that upgrading the destination is the recommended approach, but this decision requires approval from our technical supervisor.

Before proposing a solution, could you clarify two points?

1. Is there any technically viable and supported method to migrate this Nextcloud application directly from Cloudron 7.4.1 to an existing Cloudron 7.3.6 instance, without upgrading the destination?

2. If we use a recent Cloudron version, can we import the historical Nextcloud 4.17.0 application backup into an existing destination instance without affecting its other applications or users?

We will test the recommended approach in our laboratory before proposing any infrastructure changes.

Thank you again for your assistance.

Hello James, hello nebulon,

Thank you both for your replies.

To clarify, we are not trying to downgrade Cloudron because of minBoxVersion. We are reproducing an existing infrastructure in a test lab as part of my technical internship.

The actual environment consists of two Cloudron instances:

• Source: Cloudron 7.4.1, running Nextcloud 26.0.1 (package 4.17.0).
• Destination: Cloudron 7.3.6.

We have reproduced these versions on two separate physical servers to investigate the feasibility and limitations of migrating Nextcloud between them.

Our objective is to document a reliable migration procedure, preserve data integrity, and identify potential compatibility issues without affecting the existing infrastructure.

We understand that minBoxVersion: 7.3.0 specifies a minimum supported version and does not require Cloudron 7.3.6.

Given these constraints, is a migration from Cloudron 7.4.1 to 7.3.6 technically supported, or would upgrading the destination be necessary before restoring Nextcloud?

Thank you again for your help!

Hello Cloudron team,

I am working on a migration proof of concept during an IT infrastructure internship in France.

I need to reproduce an existing environment using Cloudron 7.4.1 and Nextcloud 26.0.1 (Cloudron package 4.17.0), with Cloudron 7.3.6 as the migration target.

Problem

My Cloudron 7.4.1 test instance cannot authenticate with the current Cloudron.io App Store.

• POST https://api.cloudron.io/api/v1/login returns HTTP 404 (Cannot POST /api/v1/login).
• My Cloudron.io credentials work on console.cloudron.io.
• Installing the historical Nextcloud package through the local Cloudron API returns HTTP 402: Missing token.

Already verified

• Ubuntu Server 22.04, Cloudron 7.4.1.
• The Nextcloud 4.17.0 manifest is available through the Cloudron API.
• Docker image cloudron/com.nextcloud.cloudronapp:20230420-090651-85851c598 is accessible.
• The manifest specifies minBoxVersion: 7.3.0.
• The legacy Cloudron code appears to require an App Store API token even for manifest-based installation.

Questions

1. Is there a supported method to register an existing Cloudron 7.4.1 instance with the current Cloudron.io service?
2. Can a current Cloudron.io setup token be used with this historical version?
3. Is there an officially supported way to install package 4.17.0 without upgrading Cloudron?
4. If this is no longer possible, what alternative would preserve the validity of a historical migration test?

I am not looking to bypass licensing.

Thank you for your help!