Cloudron Forum

Release v1.5.0

https://github.com/twentyhq/twenty/releases/tag/v1.5.0

I’m trying out Twenty and really looking forward to seeing it available on Cloudron soon. Its interface is friendly and modern, and the recent updates have significantly improved loading speed. Its API is very easy to integrate with external apps. Another standout point is its data model, which lets us freely customize and create objects and fields, making it simple to tailor deeply to a company’s operations.

@umnz The updates and n8n are still running very well. If it’s slow, you may need to check the RAM. Running many heavy tasks consumes a lot of RAM. Also, as I understand it, Redis is used for scaling when the current n8n server hits its limits and keeps freezing when receiving information from webhooks and running many heavy tasks at the same time.

Has anyone successfully configured Redis in n8n using the information above? Could you share the environment variables needed to set it up? Thank you very much.

Release v1.3.0

https://github.com/twentyhq/twenty/releases/tag/v1.3.0

@joseph said in Issue Starting NodeBB on Cloudron After Server Restart:

/app/pkg/start.sh

Thank you very much. I followed this guide, then adjusted the plugins to the corresponding versions and copied the appropriate package.json. The issue has been resolved

Issue Summary
I'm experiencing a critical issue with NodeBB 4.4.5 on Cloudron where the app is stuck in an infinite restart loop due to dependency conflicts. This occurs specifically after restoring from a backup that was working fine on another Cloudron server.

NodeBB App Version: 4.4.5 (latest from Cloudron App Store)
Node.js: v22.14.0
Scenario: Restored NodeBB backup from another working Cloudron server ( NodeBB 3.12.3 )

Root Cause
The backup contains package.json with dependency versions that are incompatible with NodeBB 4.4.5:

ESLint Conflict:

@stylistic/eslint-plugin-js@4.4.0 requires eslint>=9.0.0
eslint-config-airbnb-base@15.0.0 requires eslint^7.32.0 || ^8.2.0

Plugin Conflict:

nodebb-plugin-extended-markdown@2.0.1 requires nodebb-plugin-markdown@^12.0.2
But package.json has nodebb-plugin-markdown@13.2.1

The Cloudron Override Problem
Even when I manually fix package.json in Recovery Mode, Cloudron automatically overwrites it during startup with the message:
=> Bringing package.json up to speed

1. Updating package.json file with defaults... OK
   This creates an infinite restart loop:

App starts → Cloudron overwrites package.json → npm install fails → App crashes → Restart → Repeat

Error Logs
npm error ERESOLVE could not resolve
npm error While resolving: nodebb-plugin-extended-markdown@2.0.1
npm error Found: nodebb-plugin-markdown@13.2.1
npm error Could not resolve dependency:
npm error peer nodebb-plugin-markdown@"^12.0.2" from nodebb-plugin-extended-markdown@2.0.1
What I've Tried

1. Recovery Mode Fix (Temporary Success)

Successfully fixed package.json by removing conflicting dependencies
NodeBB started perfectly in Recovery Mode
Problem: Changes lost when exiting Recovery Mode due to Cloudron override

@Neiluj
Currently, I am installing Twenty using Docker Compose as shown below, but I don’t understand what needs to be done when switching to Cloudron. I hope Twenty will be integrated into Cloudron soon. After using it for a while, I found that this CRM is very powerful and customizable to serve different business needs within an enterprise.

version: '3.8'

services:
  change-vol-ownership:
    image: 'ubuntu:latest'
    user: root
    volumes:
      - 'twenty-server-local-data:/tmp/server-local-data'
      - 'twenty-docker-data:/tmp/docker-data'
    command: |
      bash -c "
        chown -R 1000:1000 /tmp/server-local-data && 
        chown -R 1000:1000 /tmp/docker-data &&
        echo 'Volume ownership changed successfully'
      "
    restart: "no"
    networks:
      - twenty-network

  db:
    image: 'twentycrm/twenty-postgres-spilo:latest'
    container_name: twenty-db
    volumes:
      - 'twenty-db-data:/home/postgres/pgdata'
    environment:
      PGUSER: postgres
      POSTGRES_PASSWORD: ${PG_DATABASE_PASSWORD:-ChangeThisPassword123!}
      POSTGRES_DB: postgres
      SPILO_ROLE: master
    networks:
      - twenty-network
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 60s

  redis:
    image: 'redis:7-alpine'
    container_name: twenty-redis
    volumes:
      - 'twenty-redis-data:/data'
    networks:
      - twenty-network
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 10s

  server:
    image: 'twentycrm/twenty:v1.1'
    container_name: twenty-server
    depends_on:
      change-vol-ownership:
        condition: service_completed_successfully
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
    volumes:
      - 'twenty-server-local-data:/app/packages/twenty-server/.local-storage'
      - 'twenty-docker-data:/app/docker-data'
    ports:
      - "${EXTERNAL_PORT:-3000}:3000"
    environment:
      NODE_PORT: 3000
      PG_DATABASE_URL: 'postgres://${PG_DATABASE_USER:-postgres}:${PG_DATABASE_PASSWORD:-ChangeThisPassword123!}@db:5432/postgres'
      SERVER_URL: '${SERVER_URL:-http://localhost:3000}'
      REDIS_URL: 'redis://redis:6379'
      APP_SECRET: '${APP_SECRET:-please-change-this-secret-key}'
      STORAGE_TYPE: '${STORAGE_TYPE:-local}'
      STORAGE_LOCAL_PATH: '${STORAGE_LOCAL_PATH:-.local-storage}'
      
      # Email Configuration
      EMAIL_DRIVER: '${EMAIL_DRIVER:-logger}'
      EMAIL_FROM_ADDRESS: '${EMAIL_FROM_ADDRESS:-noreply@localhost}'
      EMAIL_FROM_NAME: '${EMAIL_FROM_NAME:-Twenty CRM}'
      EMAIL_SMTP_HOST: '${EMAIL_SMTP_HOST:-}'
      EMAIL_SMTP_PORT: '${EMAIL_SMTP_PORT:-587}'
      EMAIL_SMTP_USER: '${EMAIL_SMTP_USER:-}'
      EMAIL_SMTP_PASSWORD: '${EMAIL_SMTP_PASSWORD:-}'
      EMAIL_SYSTEM_ADDRESS: '${EMAIL_SYSTEM_ADDRESS:-admin@localhost}'
      
      # AI Features
      IS_AI_ENABLED: '${IS_AI_ENABLED:-false}'
      OPENAI_API_KEY: '${OPENAI_API_KEY:-}'
      OPENAI_API_MODEL: '${OPENAI_API_MODEL:-gpt-4}'
      
      # Authentication
      AUTH_PASSWORD_ENABLED: '${AUTH_PASSWORD_ENABLED:-true}'
      IS_EMAIL_VERIFICATION_REQUIRED: '${IS_EMAIL_VERIFICATION_REQUIRED:-false}'
      IS_MULTIWORKSPACE_ENABLED: '${IS_MULTIWORKSPACE_ENABLED:-false}'
      
      # Rate Limiting
      API_RATE_LIMITING_LIMIT: '${API_RATE_LIMITING_LIMIT:-200}'
      API_RATE_LIMITING_TTL: '${API_RATE_LIMITING_TTL:-60}'
      
      # Tokens
      LOGIN_TOKEN_EXPIRES_IN: '${LOGIN_TOKEN_EXPIRES_IN:-30d}'
      PASSWORD_RESET_TOKEN_EXPIRES_IN: '${PASSWORD_RESET_TOKEN_EXPIRES_IN:-5m}'
      EMAIL_VERIFICATION_TOKEN_EXPIRES_IN: '${EMAIL_VERIFICATION_TOKEN_EXPIRES_IN:-24h}'
      
      # Message Queue
      MESSAGE_QUEUE_TYPE: '${MESSAGE_QUEUE_TYPE:-bull-mq}'
      
      # Features
      CALENDAR_PROVIDER_GOOGLE_ENABLED: '${CALENDAR_PROVIDER_GOOGLE_ENABLED:-false}'
      MESSAGING_PROVIDER_GMAIL_ENABLED: '${MESSAGING_PROVIDER_GMAIL_ENABLED:-false}'
      
      # OAuth (Optional)
      AUTH_GOOGLE_ENABLED: '${AUTH_GOOGLE_ENABLED:-false}'
      AUTH_GOOGLE_CLIENT_ID: '${AUTH_GOOGLE_CLIENT_ID:-}'
      AUTH_GOOGLE_CLIENT_SECRET: '${AUTH_GOOGLE_CLIENT_SECRET:-}'
      AUTH_GOOGLE_CALLBACK_URL: '${AUTH_GOOGLE_CALLBACK_URL:-}'
      
      AUTH_MICROSOFT_ENABLED: '${AUTH_MICROSOFT_ENABLED:-false}'
      AUTH_MICROSOFT_CLIENT_ID: '${AUTH_MICROSOFT_CLIENT_ID:-}'
      AUTH_MICROSOFT_CLIENT_SECRET: '${AUTH_MICROSOFT_CLIENT_SECRET:-}'
      AUTH_MICROSOFT_CALLBACK_URL: '${AUTH_MICROSOFT_CALLBACK_URL:-}'
      
    networks:
      - twenty-network
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost:3000/healthz || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 120s

  worker:
    image: 'twentycrm/twenty:v1.1'
    container_name: twenty-worker
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
      server:
        condition: service_started
    volumes:
      - 'twenty-server-local-data:/app/packages/twenty-server/.local-storage'
      - 'twenty-docker-data:/app/docker-data'
    environment:
      NODE_PORT: 3000
      PG_DATABASE_URL: 'postgres://${PG_DATABASE_USER:-postgres}:${PG_DATABASE_PASSWORD:-ChangeThisPassword123!}@db:5432/postgres'
      SERVER_URL: '${SERVER_URL:-http://localhost:3000}'
      REDIS_URL: 'redis://redis:6379'
      APP_SECRET: '${APP_SECRET:-please-change-this-secret-key}'
      STORAGE_TYPE: '${STORAGE_TYPE:-local}'
      STORAGE_LOCAL_PATH: '${STORAGE_LOCAL_PATH:-.local-storage}'
      
      # Email Configuration (same as server)
      EMAIL_DRIVER: '${EMAIL_DRIVER:-logger}'
      EMAIL_FROM_ADDRESS: '${EMAIL_FROM_ADDRESS:-noreply@localhost}'
      EMAIL_FROM_NAME: '${EMAIL_FROM_NAME:-Twenty CRM}'
      EMAIL_SMTP_HOST: '${EMAIL_SMTP_HOST:-}'
      EMAIL_SMTP_PORT: '${EMAIL_SMTP_PORT:-587}'
      EMAIL_SMTP_USER: '${EMAIL_SMTP_USER:-}'
      EMAIL_SMTP_PASSWORD: '${EMAIL_SMTP_PASSWORD:-}'
      
      # Features
      MESSAGE_QUEUE_TYPE: '${MESSAGE_QUEUE_TYPE:-bull-mq}'
      
    command: ["yarn", "worker:start"]
    networks:
      - twenty-network
    restart: unless-stopped

volumes:
  twenty-db-data:
    driver: local
  twenty-redis-data:
    driver: local
  twenty-server-local-data:
    driver: local
  twenty-docker-data:
    driver: local

networks:
  twenty-network:
    driver: bridge
    name: twenty-network

Latest Releases : 1.2.0 Jul 28th

Import Relations
When importing records, you can now import relations between records. For example, you can import a CSV file that includes a column for related records, such as linking contacts to companies or tasks to projects.

Any Field filter
We’ve added an "any field search" filter that lets you search across all fields at once. For example, it can allow you to locate a customer by their phone number, whether it's stored in the "Mobile," "Office," or "Direct Line" field.

https://twenty.com/releases

@girish

Twenty already has version 1.0. Please integrate it into Cloudron. Cloudron’s ecosystem will be much more powerful and excellent when this ecosystem is added. Twenty is finally out of beta!

https://github.com/twentyhq/twenty/releases/tag/v1.0.0

https://twenty.com/releases

@girish It seems that every time the app restarts, the nginx configuration resets to default, right? Is there any way to keep it fixed so it doesn’t change when the app restarts? Thank you.

@nebulon I tried adding both BigQuery and Postgres but couldn't connect to either. I saw logs from Cloudron indicating that the worker couldn't start.

@ChristopherMag

Could you share the reasons behind switching from Redash to Metabase?
I'm also currently evaluating Briefer: https://forum.cloudron.io/topic/12467/briefer-run-sql-and-python-and-turn-notebooks-into-dashboards
From what I understand, is Redash more suited for technical teams, while Metabase seems more user-friendly for general business users? I'd appreciate hearing about your experience with both platforms and what drove the decision to migrate.

Connection Test Failed:
Unknown error occurred while performing connection test. Please try again later

I just installed and tried running Redash, but I can't connect to any data sources.

@girish
Can you review it one more time? The software version has improved - it's now stable and receives regular updates. It has moved beyond the Beta testing phase.

0.52.0

https://twenty.com/releases

https://github.com/twentyhq/twenty/releases

@girish I added your code snippet above, and it doesn't work. But when I add a block like mine, it works.

location /mcp {
    gzip off;
    proxy_buffering off;
    proxy_cache off;
    
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    
    proxy_pass http://172.18.20.102:5678;
}

1. search for gzip_proxied any;

2. Add this location block right after the existing location block in the NGINX configuration file:

location /mcp {
gzip off;
proxy_buffering off;
proxy_cache off;

proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Host $host;

proxy_pass http://ip:5678;

}

3. After adding this code, check the NGINX configuration:

nginx -t

4. If there are no errors, reload NGINX:

systemctl reload nginx

The n8n MCP server has connected and is working properly. Thank you for your guidance. @girish

When running the new version of n8n with the MCP server, it does not work. I have identified some causes. Is it possible to configure this in Cloudron?

https://community.n8n.io/t/error-could-not-connect-to-your-mcp-server-when-integrating-external-tool-via-sse-in-ai-agent/100957/6

v0.51.0

https://github.com/twentyhq/twenty/releases