Cloudron 7.4.1 – App Store login HTTP 404 / Nextcloud 4.17.0 installation blocked

[romu79230]

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!

[james]

Hello @romu79230 and welcome to the Cloudron community forum

Please send us a mail to support@cloudron.io with the details both of your Cloudron instances.

[nebulon]

hm that is a tough issue. Those cloudron.io APIs don't exist anymore so that will not work without updating Cloudron (probably manually).

Cloudron generally is designed to be more of an evergreen platform, mostly because server software exposed to the internet always need to be kept fresh because of security issues.

I guess one alternative around this to still use the old nextlcoud, you could build the tag from the nextcloud package repo https://git.cloudron.io/packages/nextcloud-app If that still builds is a bit unknown given that this also requires other upstream resources to be installed, but probably worth a try.

[james]

Hello @romu79230

@romu79230 said:

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.

Am I reading this correct that you are trying to migrate from 7.4.1 to 7.3.6? So a downgrade?
Why do that?
Did you maybe misunderstand minBoxVersion: 7.3.0 in the sense that the version 7.3 is needed?
It is the minimal version required. So if you install the latest version of Cloudron you can also run Nextcloud 4.17.0.

[romu79230]

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!

[james]

Hello @romu79230

Both of your existing servers are extremely outdated.

• Cloudron version 7.3.6 https://forum.cloudron.io/topic/8268/cloudron-7-3-released
• Cloudron version 7.4.1 https://forum.cloudron.io/topic/9179/cloudron-7-4-released

Both from 2022/2023 and did not update Cloudron since then.

@romu79230 said:

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?

Yes and No.

Yes you should upgrade your servers to the latest Cloudron version.
Is it needed to test a migration from server A=>B, no.

When you install a new Cloudron server, with the latest Cloudron version you can install Nextcloud version 4.17.0 and then import the backup config from the production Cloudron.
This way you can test a migration from the production Cloudron server 7.4.1 to a fresh latest version Cloudron.

I want to clarify and understand the following:

@romu79230 said:

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

Why would you want to migrate a Nextcloud app from one outdated Cloudron to an even more outdated Cloudron?