Bug Reports

cargue Supabase y se bloqueo easypanel ahira ya no me deja entrar tampoco si quiero cargar una aplicacion me podrian ayudar?

Hola, Cuando se reinicia el servidor fisico, al cargar nuevamente el contenedor de easypanel se estan perdiendo las llaves ssh generadas para sincronizar desde un repositorio de azure devops. intente agregar el certificado que easypanel genera, sin embargo, este certificado no es permitido por devops. que documentacion me pueden compartir o de que forma puedo tener el certificado persistente y tener integracion entre easypanel y devops. estoy usando la funcionalidad de source usando git y cargando el dockerfile que yo tengo en el repositorio para generar un contenedor con mi solucion. muchisimas gracias por tan excelente producto. quedo atento.

I can't use upload image because it always error 500 with default settings minio endpoint S3_ENDPOINT=http://$(PROJECT_NAME)_typebot-minio:9001 What's the correct endpoint?

The JWT is not working in Supabase for API integration and user creation.

Cal.com container never starts when creating it.

Describe the bug Scheduled backups for PostgreSQL are failing because the backup command wrongly uses the username as the database name. To Reproduce Configure PostgreSQL service with: - Username: ProdAdminPostGres01 - Database name: easyflow-prod Define scheduled backup (cron) in UI. Save and check logs or wait for schedule. Observed behavior Logs show: psql -U ProdAdminPostGres01 -d ProdAdminPostGres01 Which fails with: FATAL: database "ProdAdminPostGres01" does not exist Manual backups work correctly. Expected behavior Scheduled backups should use the configured database name ( easyflow-prod ), not the username. CLI confirmation Inside /etc/easypanel/data/data.mdb the variables are set correctly: DBUSER="ProdAdminPostGres01" DBNAME="easyflow-prod" So the bug is in scheduler command generation. Environment: * EasyPanel v2.20.1 * Postgres 17.4-alpine * Backup provider: Google Drive Logs: * Error from CLI: FATAL: database "ProdAdminPostGres01" does not exist Additional context Automatic scheduled backups fail; manual backups succeed. Looks like scheduler improperly binds DBUSER instead of DBNAME . Please let me know if you need more logs or diagnostics. Thanks!

When moving an application that uses a custom domain to another project, the domain is not automatically transferred with the application. If you try to add the same domain to the new project, an error appears stating that the domain already exists. To resolve this issue, you must manually remove the domain from the app in the original project before adding it to the new one. The same thing happens with backups — they are not automatically transferred between projects and must be again recreated.

Installed nodebb. Admin panel said "running version 1.19.7", upgrade to 3.10.3. I followed instuctions ... bash -5c8782edea7f:/# curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash - sudo apt-get install -y nodejs bash: curl: command not found bash: sudo: command not found bash: sudo: command not found

In the projects laravel make mode box. In the Environment doesn't catch change of environment made by dashboard easypanel.

Deploying migrations for postgresql Database URL: > evolution-api@2.2.3 db:deploy > node runWithProvider.js "rm -rf ./prisma/migrations && cp -r ./prisma/DATABASE_PROVIDER-migrations ./prisma/migrations && npx prisma migrate deploy --schema ./prisma/DATABASE_PROVIDER-schema.prisma" Environment variables loaded from .env Prisma schema loaded from prisma/postgresql-schema.prisma Datasource "db": PostgreSQL database "evolution3", schema "public" at "evolution3_postgres:5432" 49 migrations found in prisma/migrations No pending migrations to apply. npm notice npm notice New major version of npm available! 10.8.2 -> 11.4.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.4.2 npm notice To update run: npm install -g npm@11.4.2 npm notice Migration succeeded > evolution-api@2.2.3 db:generate > node runWithProvider.js "npx prisma generate --schema ./prisma/DATABASE_PROVIDER-schema.prisma" Environment variables loaded from .env Prisma schema loaded from prisma/postgresql-schema.prisma ✔ Generated Prisma Client (v6.3.0) to ./node_modules/@prisma/client in 1.06s Start by importing your Prisma Client (See: https://pris.ly/d/importing-client ) Tip: Curious about the SQL queries Prisma ORM generates? Optimize helps you enhance your visibility: https://pris.ly/tip-2-optimize Prisma generate succeeded > evolution-api@2.2.3 start:prod > node dist/main [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheEngine] [string] RedisCache initialized for groups [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheService] [string] cacheservice created using cache engine: Gt [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheEngine] [string] RedisCache initialized for instance [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheService] [string] cacheservice created using cache engine: Gt [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheEngine] [string] RedisCache initialized for baileys [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [CacheService] [string] cacheservice created using cache engine: Gt [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 INFO [WA MODULE] [string] Module - ON [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [Redis] [string] redis connecting [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:35 VERBOSE [Redis] [string] redis ready [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:36 INFO [PrismaRepository] [string] Repository:Prisma - ON [Evolution API] v2.2.3 164 - Thu Jun 19 2025 06:54:36 LOG [SERVER] [string] HTTP - ON: 8080