Cloudron Forum

Definitely Cloudflare if .com, .net etc... Can't beat their pricing! For other domain extensions, Namesilo.

I have been able to find a turnaround for exporting the schema using Node.js.

===========
To export your schema from a Directus instance using Node.js

Prerequisites

• Node.js Installed: Ensure Node.js is installed on your system.
• Directus Instance and Token: Obtain your source Directus project URL and access token.

Steps to Export the Schema

1. Setup Node.js Project:

   • Create a new directory and initialize a Node.js project:

     mkdir directus-schema-export
     cd directus-schema-export
     npm init -y
     

   • Install the required package:

     npm install cross-fetch
     

2. Create the Script:

   • Create a file, e.g., export-schema.js, and add the following code:

     const fetch = require('cross-fetch');
     
     // Replace with your actual Directus project URL and access token
     const SOURCE_URL = 'https://your-directus-instance.com'; // Your Directus URL
     const SOURCE_TOKEN = 'your-access-token'; // Your Directus access token
     
     async function exportSchema() {
       try {
         const response = await fetch(`${SOURCE_URL}/schema/snapshot?access_token=${SOURCE_TOKEN}`);
         if (!response.ok) {
           throw new Error(`Failed to fetch schema: ${response.statusText}`);
         }
         const { data } = await response.json();
         console.log('Schema exported successfully:', data);
         return data;
       } catch (error) {
         console.error('Error exporting schema:', error.message);
       }
     }
     
     // Call the function
     exportSchema();
     

3. Run the Script:

   • Execute the script using Node.js:

     node export-schema.js
     

   • The schema will be logged to the console. You can redirect it to a file:

     node export-schema.js > schema.json
     

Hi,

Currently the only method to export the data model structure in Directus is through the CLI. However, due to read access limitation in Cloudron, this is not working.

Reference: https://www.restack.io/docs/directus-knowledge-directus-export-schema-guide

So how I can export it then?

Thanks

@nebulon Yes OpenAI works with other app.

I've been able to recover my admin account by creating a new admin account using the CLI (Thanks for the steps to follow!)

Then I realized my mistake.. in my account profile, I did set the provider to "Cloudron" instead of "Default". It's why I wasn't able to log in back into my account. I switched it back to Default with my new admin account and now I'm able to log in!

Thanks again for your support

@nebulon Okay I will check on Directus side for the connection issue.

For OpenID, for some reason I'm unable to log in with my Cloudron admin user.. when I choose "Log in via Cloudron", it says service unavailable.

I have seen in the Cloudron documentation for Directus that Cloudron users inherited automatically the administrator role.. so if I can make the Cloudron integration work, I could create a new administrator user and get my issue fixed quickly.

@nebulon I want to add that the problem only affects the superadmin user... my other users work great! Can we restore the OpenID integration so I can log in via Cloudron and then create a new administrator?

@nebulon

I've been able to change the password using CLI following your commands, however, I'm still unable to log into Directus. Still says wrong username or password.

I confirm no changes or updates have been made to Cloudron or Directus since the 20th December... and on 27th everything was still working fine.

@robi I tried but this hasn't resolved my problem. Thanks for the suggestion tho.

@robi I see a green button "Postgres" and when I click on it, It pastes this in the terminal:

PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE}

But I know that Directus backend uses Postgres as database, but this env variable is hardcoded from what I've seen so even if I would like to change it, it's maintained by Cloudron directly.

I think my issue that I'm unable to log in is related to this environment variable that is missing somehow. Looking forward to the fix from the Cloudron support team.

Quick update... I tried to reset the password via CLI using this command:

npx directus users passwd --email <user-email> --password <new-password>

But it return this error:
[16:29:48.570] ERROR: "DB_CLIENT" Environment Variable is missing.

Other CLI commands also return this error.

Seeing this in the logs:

Dec 30 10:01:01 "message": "Invalid user credentials.",
Dec 30 10:01:01 "stack":
Dec 30 10:01:01 DirectusError: Invalid user credentials.
Dec 30 10:01:01 at AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:81:19)
Dec 30 10:01:01 at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/local.js:70:56
Dec 30 10:01:01 "name": "DirectusError",
Dec 30 10:01:01 "code": "INVALID_CREDENTIALS",
Dec 30 10:01:01 "status": 401
Dec 30 10:01:01 }
Dec 30 10:03:11 [15:03:11.168] DEBUG: Invalid user credentials.
Dec 30 10:03:11 err: {
Dec 30 10:03:11 "type": "",
Dec 30 10:03:11 "message": "Invalid user credentials.",
Dec 30 10:03:11 "stack":
Dec 30 10:03:11 DirectusError: Invalid user credentials.
Dec 30 10:03:11 at AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:81:19)
Dec 30 10:03:11 at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/local.js:70:56
Dec 30 10:03:11 "name": "DirectusError",
Dec 30 10:03:11 "code": "INVALID_CREDENTIALS",
Dec 30 10:03:11 "status": 401
Dec 30 10:03:11 }
Dec 30 10:03:11 [15:03:11] POST /auth/login 401 509ms
Dec 30 10:03:12 [15:03:12] GET /auth/login/cloudron?redirect=https%3A%2F%2F****.*********.com%2Fadmin%2Flogin%3Freason%3DSIGN_OUT%26continue%3D 302 11ms
Dec 30 10:03:13 [15:03:13.779] DEBUG: [OpenID] Configured group claim with name "groups" does not exist or is empty.
Dec 30 10:03:13 [15:03:13.805] WARN: [OpenID] Unknown OP error
Dec 30 10:03:13 err: {
Dec 30 10:03:13 "type": "OPError",
Dec 30 10:03:13 "message": "unauthorized_client (requested grant type is not allowed for this client)",
Dec 30 10:03:13 "stack":
Dec 30 10:03:13 OPError: unauthorized_client (requested grant type is not allowed for this client)
Dec 30 10:03:13 at processResponse (/app/code/node_modules/openid-client/lib/helpers/process_response.js:38:13)
Dec 30 10:03:13 at Client.grant (/app/code/node_modules/openid-client/lib/client.js:1381:22)
Dec 30 10:03:13 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Dec 30 10:03:13 at async Client.refresh (/app/code/node_modules/openid-client/lib/client.js:1125:22)
Dec 30 10:03:13 at async OpenIDAuthDriver.refresh (file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:244:34)
Dec 30 10:03:13 at async AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:111:13)
Dec 30 10:03:13 at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:333:28
Dec 30 10:03:13 "error": "unauthorized_client",
Dec 30 10:03:13 "error_description": "requested grant type is not allowed for this client",
Dec 30 10:03:13 "name": "OPError"
Dec 30 10:03:13 }
Dec 30 10:03:14 [15:03:14.214] WARN: Service "openid" is unavailable. Service returned unexpected response: requested grant type is not allowed for this client.
Dec 30 10:03:14 err: {
Dec 30 10:03:14 "type": "",
Dec 30 10:03:14 "message": "Service \"openid\" is unavailable. Service returned unexpected response: requested grant type is not allowed for this client.",
Dec 30 10:03:14 "stack":
Dec 30 10:03:14 DirectusError: Service "openid" is unavailable. Service returned unexpected response: requested grant type is not allowed for this client.
Dec 30 10:03:14 at handleError (file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:268:16)
Dec 30 10:03:14 at OpenIDAuthDriver.refresh (file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:253:23)
Dec 30 10:03:14 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Dec 30 10:03:14 at async AuthenticationService.login (file:///app/code/node_modules/@directus/api/dist/services/authentication.js:111:13)
Dec 30 10:03:14 at async file:///app/code/node_modules/@directus/api/dist/auth/drivers/openid.js:333:28
Dec 30 10:03:14 "name": "DirectusError",
Dec 30 10:03:14 "extensions": {
Dec 30 10:03:14 "service": "openid",
Dec 30 10:03:14 "reason": "Service returned unexpected response: requested grant type is not allowed for this client"
Dec 30 10:03:14 },
Dec 30 10:03:14 "code": "SERVICE_UNAVAILABLE",
Dec 30 10:03:14 "status": 503
Dec 30 10:03:14 }
Dec 30 10:03:14 [15:03:14] GET /auth/login/cloudron/callback?code=*************&state=*************&iss=https%3A%2F%2Fmy.*********.com%2Fopenid 302 510ms
Dec 30 10:03:14 [15:03:14] GET /admin/login?reason=SERVICE_UNAVAILABLE 200 2ms
Dec 30 10:03:14 [15:03:14.847] DEBUG: Invalid payload. The refresh token is required in either the payload or cookie.
Dec 30 10:03:14 err: {
Dec 30 10:03:14 "type": "",
Dec 30 10:03:14 "message": "Invalid payload. The refresh token is required in either the payload or cookie.",
Dec 30 10:03:14 "stack":
Dec 30 10:03:14 DirectusError: Invalid payload. The refresh token is required in either the payload or cookie.
Dec 30 10:03:14 at file:///app/code/node_modules/@directus/api/dist/controllers/auth.js:89:15
Dec 30 10:03:14 at file:///app/code/node_modules/@directus/api/dist/utils/async-handler.js:1:66
Dec 30 10:03:14 at Layer.handle [as handle_request] (/app/code/node_modules/express/lib/router/layer.js:95:5)
Dec 30 10:03:14 at next (/app/code/node_modules/express/lib/router/route.js:149:13)
Dec 30 10:03:14 at Route.dispatch (/app/code/node_modules/express/lib/router/route.js:119:3)
Dec 30 10:03:14 at Layer.handle [as handle_request] (/app/code/node_modules/express/lib/router/layer.js:95:5)
Dec 30 10:03:14 at /app/code/node_modules/express/lib/router/index.js:284:15
Dec 30 10:03:14 at Function.process_params (/app/code/node_modules/express/lib/router/index.js:346:12)
Dec 30 10:03:14 at next (/app/code/node_modules/express/lib/router/index.js:280:10)
Dec 30 10:03:14 at Function.handle (/app/code/node_modules/express/lib/router/index.js:175:3)
Dec 30 10:03:14 "name": "DirectusError",
Dec 30 10:03:14 "extensions": {
Dec 30 10:03:14 "reason": "The refresh token is required in either the payload or cookie"
Dec 30 10:03:14 },
Dec 30 10:03:14 "code": "INVALID_PAYLOAD",
Dec 30 10:03:14 "status": 400
Dec 30 10:03:14 }

Hi,

Last week, I worked 2 days to set up my database structure in Directus and logged in/out at multiple attempts using my superadmin email and password.

Today, I am trying to log in and it says credentials invalid? I tried to reset the password but despite using the reset password link received in the email and seeing a message "Your password has been changed successfully", I'm still unable to log in.

The option to log in via Cloudron is also not working, it says "Service unavailable". Pls how I can restore my superadmin access? I have spent way too many hours here to start over.

Thanks!

@nebulon Okay thanks!

I just realized that it's not only a matter of migration... They refactored the API too, meaning that I will have to recode my app. Hmmm. OK

@nebulon said in PocketBase is now available:

anually if needed, since

Okay, but if I install the current version and use it in production.. and the 0.23 with the refactored codes becomes stable in a few months, will you support the upgrade?

I guess if you added it on the marketplace it's because you planned to support it long-term, correct?

I think it's a good thing to have PocketBase because Directus is overkill for many projects.

@robi Well if I'm using Cloudron its exactly to avoid relying on other hosting services ^^ but thanks for sharing. Maybe other people could be interested.

@girish Can you confirm that Cloudron will support the migration/upgrade to 0.23 when this will be stable and released? If yes, than I will install it right away as I have a very good use cases for it. I'm just a bit worried about the code revamp and I couldn't proceed with the upgrade myself. That would be great if Cloudron team could support the upgrade when it will be available and stable. Thanks!

I am following this platform for a while... I am surprised to see it arriving on Cloudron as the dev is planning a big framework code update and the migration will be very complex... That's the main reason why I didn't go with this backend for a project because otherwise, it look amazing!

How Cloudron plan to manage this big upgrade when it will comes? From what I've read from the founder, the upgrade won't be able to be done automatically and it was too complex for my skills (non-coder).

From its creator:

< There will be major breaking changes to the Go and JSVM (pb_hooks/pb_migrations) APIs.
An upgrade guide listing all changes will be available but it will require users to perform manual code migration steps (only the pb_data will be automigrated). >

Reference:
https://github.com/pocketbase/pocketbase/discussions/5543
https://github.com/pocketbase/pocketbase/discussions/4355

Adding max_old_space_size to my .env solved the issue yay 🥳

I just tried to add this to my .env file:

NODE_OPTIONS=--max_old_space_size=8192

I will launch a new run and if this solves the problem, I'll keep you posted!

@joseph I only see this in Chrome console:

pushConnection.store-BrFt2YWH.js:54 WebSocket connection to 'wss://n8n.*************.com/rest/push?pushRef=abufwmz0xm' failed:
pushConnect @ pushConnection.store-BrFt2YWH.js:54

My n8n instance is 8g and the graph history barely exceeds 2g.

I'm seeing this in the logs but I'm not sure if it's related to my workflow that crashes:

2024-12-20T05:32:35Z ----- Native stack trace -----
2024-12-20T05:32:35Z 10: 0x709bdded9ef6
2024-12-20T05:32:35Z 1: 0xb8ced1 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2024-12-20T05:32:35Z 2: 0xf06460 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
2024-12-20T05:32:35Z 3: 0xf06747 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
2024-12-20T05:32:35Z 4: 0x11182e5  [node]
2024-12-20T05:32:35Z 5: 0x1130168 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
2024-12-20T05:32:35Z 6: 0x1106281 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2024-12-20T05:32:35Z 7: 0x1107415 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2024-12-20T05:32:35Z 8: 0x10e4a66 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
2024-12-20T05:32:35Z 9: 0x1540896 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
2024-12-20T05:32:35Z <--- JS stacktrace --->
2024-12-20T05:32:35Z <--- Last few GCs --->
2024-12-20T05:32:35Z FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2024-12-20T05:32:35Z [1:0x12d66f70] 19549759 ms: Scavenge 1975.3 (2077.8) -> 1971.8 (2078.3) MB, 6.37 / 0.00 ms  (average mu = 1.000, current mu = 1.000) task;
2024-12-20T05:32:35Z [1:0x12d66f70] 19554444 ms: Scavenge 1977.4 (2079.7) -> 1974.6 (2081.7) MB, 7.13 / 0.01 ms  (average mu = 1.000, current mu = 1.000) task;
2024-12-20T05:32:35Z [1:0x12d66f70] 19556720 ms: Scavenge 1982.6 (2083.6) -> 1978.1 (2100.6) MB, 10.54 / 0.00 ms  (average mu = 1.000, current mu = 1.000) allocation failure;
2024-12-20T05:32:36Z => Ensure directories
2024-12-20T05:32:36Z => Loading configuration
2024-12-20T05:32:36Z => Setting permissions
2024-12-20T05:32:37Z => Starting N8N
2024-12-20T05:32:38Z Permissions 0644 for n8n settings file /app/data/user/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
2024-12-20T05:32:38Z Loaded config overwrites from /app/data/configs/default.json
2024-12-20T05:32:38Z User settings loaded from: /app/data/user/.n8n/config
2024-12-20T05:32:40.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.18.84:5678
2024-12-20T05:32:40Z Last session crashed
2024-12-20T05:32:50.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.18.84:5678
2024-12-20T05:32:50Z Initializing n8n process
2024-12-20T05:32:51Z 
2024-12-20T05:32:51Z 
2024-12-20T05:32:51Z - N8N_CONFIG_FILES -> Please use .env files or *_FILE env vars instead.
2024-12-20T05:32:51Z The following environment variable is deprecated and will be removed in an upcoming version of n8n. Please take the recommended actions to update your configuration:
2024-12-20T05:32:51Z n8n ready on 0.0.0.0, port 5678