Account deleted? RepoCloud shows paused

[Sandra_R_C_O_O_N]

Hello everyone,

I’m hoping someone has encountered a case like this before.

I created an n8n instance via RepoCloud about 3 months ago (for a course and some test workflows). Now I’m trying to access it again and I’m stuck.

Current status:

• My RepoCloud project still exists and is named teamies_weekly.
• The status in RepoCloud is “Paused”.
• The project is still displayed.
• The original deployment email from RepoCloud contains the URL:
  xgxauq46.rpcld.co
• This URL no longer works today and returns:
  ERR_NAME_NOT_RESOLVED
• In the RepoCloud project, the “RepoCloud URL” field is empty.
• There is no button like Resume, Start or Restart, only Delete Server.
• I can log in to RepoCloud itself normally.

Additionally, I continue to receive emails from n8n (Security Updates, Newsletters, etc.) to the same email address.

What confuses me:

• When I try to request a Magic Link via n8n Cloud because I no longer remember my account name, no email arrives.
• At the same time, my email address seems to be known to n8n, as I continue to receive messages from n8n.
• I can no longer create a new trial with the email address I used back then s.perdacher@googlemail.com.

My questions:

1. Does this look like an expired trial instance to you or rather like a deleted deployment?
   I somehow didn’t receive any emails about this.
2. If the original URL can no longer be resolved, is there still a chance that the workflows/database still exist?
3. Has anyone experienced a RepoCloud project still being visible even though the actual n8n instance is no longer accessible?
4. Is there a way to find out whether the data still exists or can be recovered?

Thank you for any helpful information!

[kjooleng]

Hi @Sandra_R_C_O_O_N

The reason you aren’t receiving a Magic Link and cannot start a new trial at n8n.io is that you are trying to log into n8n Cloud (the hosted SaaS version).

However, you deployed your instance via RepoCloud. RepoCloud provides a way to self-host n8n on their infrastructure. This means your n8n instance is a standalone installation; it is not an n8n Cloud account.

This is what you can do:

1. Stop trying to recover the account via n8n.io (it won’t work).
2. Contact RepoCloud support immediately.
3. Check your RepoCloud billing/email history for any “Trial Expired” or “Payment Failed” notifications that might have gone to spam.

[shedrach]

@kjooleng

The reason you aren’t receiving a Magic Link and cannot start a new trial at n8n.io is that you are trying to log into n8n Cloud (the hosted SaaS version).

However, you deployed your instance via RepoCloud. RepoCloud provides a way to self-host n8n on their infrastructure. This means your n8n instance is a standalone installation; it is not an n8n Cloud account.

This is what you can do:

1. Stop trying to recover the account via n8n.io (it won’t work).
2. Contact RepoCloud support immediately.
3. Check your RepoCloud billing/email history for any “Trial Expired” or “Payment Failed” notifications that might have gone to spam.

Based on what you’ve described, this looks much more like a RepoCloud deployment issue than an n8n Cloud account issue.

A few things stand out:

• The fact that your RepoCloud project teamies_weekly is still visible suggests RepoCloud still has a record of the deployment, but the empty “RepoCloud URL” field and the ERR_NAME_NOT_RESOLVED error indicate the underlying server or DNS record is no longer active.

• Since the project status is “Paused” and you only see a “Delete Server” option, it’s possible the original instance was automatically suspended or removed after a trial period, inactivity, or a billing-related event. In some hosting platforms, the project metadata remains visible even after the actual runtime environment has been decommissioned.

• The n8n newsletters and security update emails are not necessarily evidence that your n8n instance still exists. Those are often sent from marketing or notification systems that are separate from both n8n Cloud accounts and self-hosted deployments.

• The missing Magic Link email is expected if this was never an n8n Cloud workspace. A RepoCloud-hosted n8n instance is independent of n8n Cloud authentication, so recovery through n8n.io usually won’t help in this scenario.

Regarding your workflows and database: there is still a possibility they exist, but only RepoCloud can confirm that. If the deployment was merely paused, the data volume may still be attached. If the server was fully deleted, recovery depends on whether RepoCloud keeps backups or snapshots after suspension.

My recommendation would be:

1. Contact RepoCloud support directly and provide:

   • Project name: teamies_weekly

   • Original URL: xgxauq46.rpcld.co

   • Approximate creation date

   • Email address associated with the deployment

2. Ask specifically:

   • Whether the deployment was paused, suspended, or deleted

   • Whether the database volume still exists

   • Whether any backups or snapshots are available

   • Whether the original URL can be restored or replaced

3. Check your spam/junk folders and billing history for any messages related to trial expiration, resource cleanup, suspension policies, or failed payments.

Until RepoCloud confirms the status of the deployment, I wouldn’t assume the data is lost. The project still being visible is at least a positive sign that there may be deployment metadata or attached storage that can potentially be recovered.

[Merrill]

The newsletters and security emails you’re still receiving from n8n are coming from their marketing system, they’re not tied to your instance being alive. So unfortunately that’s not a sign your deployment is still running.

[shedrach]

One thing I’d add to what’s already been mentioned: the biggest clue here is the combination of “Paused” status + empty RepoCloud URL + DNS resolution failure.

Normally, if an n8n instance is simply stopped, you can often restart it and the URL remains associated with the deployment. The fact that the URL field itself is blank suggests the deployment record may still exist while the underlying runtime or networking resources were detached at some point.

Before assuming the workflows are gone, I’d verify a few things in RepoCloud:

• Check whether there is a “Resume”, “Redeploy”, “Rebuild”, or “Clone” option hidden in the project settings.

• Look for attached resources (volumes, databases, persistent storage, snapshots, backups). In many hosted environments, storage survives longer than the application container itself.

• Review billing history and account notifications around the time the instance was last active. Some platforms automatically archive or remove compute resources after trial expiration while retaining project metadata.

• If you originally connected the instance to GitHub, check whether the deployment configuration still references the repository. That can help support identify the original environment faster.

When contacting RepoCloud support, I’d specifically ask:

1. Does the project still have an attached persistent volume?

2. Was the server paused, archived, or permanently deleted?

3. Is there a snapshot/backup retention policy for expired trial deployments?

4. Can the deployment be recreated from the existing project metadata?

The good news is that seeing the project name still present is usually better than seeing the project completely disappear. It doesn’t guarantee the workflows are recoverable, but it does suggest there may still be metadata, storage, or deployment records that support can inspect.

At this point, RepoCloud is really the only party that can confirm whether the underlying n8n data still exists, since this deployment was independent of n8n Cloud.