Lago

The signup.rake task uses create_with, which only sets the password on user creation. If the user already exists, restarts after password changes leave the old password in place, causing "incorrect login or password". To fix permanently, modify lib/tasks/signup.rake to use find_or_initialize_by, set password explicitly, then save. As a quick workaround, delete the existing user (rails console: User.find_by(email: ENV['LAGO_ORG_USER_EMAIL'])&.destroy) and re-run the signup rake task, or update the password directly in the database. The fix ensures the password stays synced with the env var across restarts.

This error occurs because the structure.sql file in Lago attempts to DROP TRIGGER on the payment_receipts table before it is created. A workaround is to manually create the table first: 'CREATE TABLE IF NOT EXISTS public.payment_receipts (id uuid DEFAULT gen_random_uuid() NOT NULL, number character varying NOT NULL, payment_id uuid NOT NULL, organization_id uuid NOT NULL, created_at timestamp(6) without time zone NOT NULL, updated_at timestamp(6) without time zone NOT NULL, billing_entity_id uuid NOT NULL);' Then run db:schema:load or db:migrate. The issue was reported on Lago v1.33.4 and v1.38.0. The maintainers could not reproduce it in the latest version, so upgrading may resolve it.