starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1761] Elements in SignUp and Login not working #505

New issue

Closed

opened 2026-02-26 18:47:20 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:47:20 +03:00

Owner

Originally created by @FilyBox on GitHub (Apr 25, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1761

Issue Description

Description:

I'm currently unable to get the login or signup functionality working.

Clicking on "Sign Up" just reloads the page without performing any validation.

When trying to create a new user, the "Next" button doesn't do anything and the SignaturePadDialog isn't working either, the SignaturePadDialog is just there empty.

It seems like no form actions or button handlers are working at all in the project.

I tried adding some console.log statements to debug the process, but none of them are triggered — it looks like no functions are being executed.

My environment matches the one described in the "Get Started" section. I'm running the project in a Docker container, and the only difference is that I'm using Neon as my database. However, I don’t believe the issue is related to the database, since no frontend actions are triggered at all.

Is there something I might be missing in the setup proccess?
my .env file:
`# AUTH
NEXTAUTH_SECRET="secret"

CRYPTO

Application Key for symmetric encryption and decryption

REQUIRED: This should be a random string of at least 32 characters

NEXT_PRIVATE_ENCRYPTION_KEY="CAFEBABE"

REQUIRED: This should be a random string of at least 32 characters

NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY="DEADBEEF"

AUTH OPTIONAL

Find documentation on setting up Google OAuth here:

https://docs.documenso.com/developers/self-hosting/setting-up-oauth-providers#google-oauth-gmail

NEXT_PRIVATE_GOOGLE_CLIENT_ID=""
NEXT_PRIVATE_GOOGLE_CLIENT_SECRET=""

NEXT_PRIVATE_OIDC_WELL_KNOWN=""
NEXT_PRIVATE_OIDC_CLIENT_ID=""
NEXT_PRIVATE_OIDC_CLIENT_SECRET=""
NEXT_PRIVATE_OIDC_PROVIDER_LABEL=""
NEXT_PRIVATE_OIDC_SKIP_VERIFY=""

NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET=mytestApp

POSTGRES_USER="documenso"
POSTGRES_PASSWORD="password"
POSTGRES_DB="documenso"

URLS

NEXT_PUBLIC_WEBAPP_URL="http://localhost:3000"

URL used by the web app to request itself (e.g. local background jobs)

NEXT_PRIVATE_INTERNAL_WEBAPP_URL="http://localhost:3000"

DATABASENEXT_PRIVATE_DATABASE_URL="postgres://documenso:password@database:5432/documenso"

NEXT_PRIVATE_DATABASE_URL="My Database"

Defines the URL to use for the database when running migrations and other commands that won't work with a connection pool.

NEXT_PRIVATE_DIRECT_DATABASE_URL="My Database"

SIGNING

The transport to use for document signing. Available options: local (default) | gcloud-hsm

NEXT_PRIVATE_SIGNING_TRANSPORT="local"

OPTIONAL: The passphrase to use for the local file-based signing transport.

NEXT_PRIVATE_SIGNING_PASSPHRASE=

OPTIONAL: The local file path to the .p12 file to use for the local signing transport.

NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH=

OPTIONAL: The base64-encoded contents of the .p12 file to use for the local signing transport.

NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS=

OPTIONAL: The path to the Google Cloud HSM key to use for the gcloud-hsm signing transport.

NEXT_PRIVATE_SIGNING_GCLOUD_HSM_KEY_PATH=

OPTIONAL: The path to the Google Cloud HSM public certificate file to use for the gcloud-hsm signing transport.

NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_PATH=

OPTIONAL: The base64-encoded contents of the Google Cloud HSM public certificate file to use for the gcloud-hsm signing transport.

NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_CONTENTS=

OPTIONAL: The path to the Google Cloud Credentials file to use for the gcloud-hsm signing transport.

NEXT_PRIVATE_SIGNING_GCLOUD_APPLICATION_CREDENTIALS_CONTENTS=

STORAGE

OPTIONAL: Defines the storage transport to use. Available options: database (default) | s3

NEXT_PUBLIC_UPLOAD_TRANSPORT="database"

OPTIONAL: Defines the endpoint to use for the S3 storage transport. Relevant when using third-party S3-compatible providers.

NEXT_PRIVATE_UPLOAD_ENDPOINT="http://127.0.0.1:9002"

OPTIONAL: Defines the force path style to use for the S3 storage transport. Relevant when using third-party S3-compatible providers.

This will change it from using virtual hosts .domain.com/ to fully qualified paths domain.com//

NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE="false"

OPTIONAL: Defines the region to use for the S3 storage transport. Defaults to us-east-1.

NEXT_PRIVATE_UPLOAD_REGION="unknown"

REQUIRED: Defines the bucket to use for the S3 storage transport.

NEXT_PRIVATE_UPLOAD_BUCKET="documenso"

OPTIONAL: Defines the access key ID to use for the S3 storage transport.

NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID="documenso"

OPTIONAL: Defines the secret access key to use for the S3 storage transport.

NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY="password"

SMTP

OPTIONAL: Defines the transport to use for sending emails. Available options: smtp-auth (default) | smtp-api | mailchannels

NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"

OPTIONAL: Defines the host to use for sending emails.

NEXT_PRIVATE_SMTP_HOST="127.0.0.1"

OPTIONAL: Defines the port to use for sending emails.

NEXT_PRIVATE_SMTP_PORT=2500

OPTIONAL: Defines the username to use with the SMTP server.

NEXT_PRIVATE_SMTP_USERNAME="documenso"

OPTIONAL: Defines the password to use with the SMTP server.

NEXT_PRIVATE_SMTP_PASSWORD="password"

OPTIONAL: Defines the API key user to use with the SMTP server.

NEXT_PRIVATE_SMTP_APIKEY_USER=

OPTIONAL: Defines the API key to use with the SMTP server.

NEXT_PRIVATE_SMTP_APIKEY=

OPTIONAL: Defines whether to force the use of TLS.

NEXT_PRIVATE_SMTP_SECURE=

OPTIONAL: if this is true and NEXT_PRIVATE_SMTP_SECURE is false then TLS is not used even if the server supports STARTTLS extension

NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS=

REQUIRED: Defines the sender name to use for the from address.

NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"

REQUIRED: Defines the email address to use as the from address.

NEXT_PRIVATE_SMTP_FROM_ADDRESS="noreply@documenso.com"

OPTIONAL: Defines the service for nodemailer

NEXT_PRIVATE_SMTP_SERVICE=

OPTIONAL: The API key to use for Resend.com

NEXT_PRIVATE_RESEND_API_KEY=

OPTIONAL: The API key to use for MailChannels.

NEXT_PRIVATE_MAILCHANNELS_API_KEY=

OPTIONAL: The endpoint to use for the MailChannels API if using a proxy.

NEXT_PRIVATE_MAILCHANNELS_ENDPOINT=

OPTIONAL: The domain to use for DKIM signing.

NEXT_PRIVATE_MAILCHANNELS_DKIM_DOMAIN=

OPTIONAL: The selector to use for DKIM signing.

NEXT_PRIVATE_MAILCHANNELS_DKIM_SELECTOR=

OPTIONAL: The private key to use for DKIM signing.

NEXT_PRIVATE_MAILCHANNELS_DKIM_PRIVATE_KEY=

OPTIONAL: Displays the maximum document upload limit to the user in MBs

NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=5

STRIPE

NEXT_PRIVATE_STRIPE_API_KEY=
NEXT_PRIVATE_STRIPE_WEBHOOK_SECRET=

BACKGROUND JOBS

NEXT_PRIVATE_JOBS_PROVIDER="local"
NEXT_PRIVATE_INNGEST_EVENT_KEY=

FEATURES

OPTIONAL: Leave blank to disable PostHog and feature flags.

NEXT_PUBLIC_POSTHOG_KEY=""

OPTIONAL: Leave blank to disable billing.

NEXT_PUBLIC_FEATURE_BILLING_ENABLED=

NEXT_PUBLIC_DISABLE_SIGNUP="false"

E2E Tests

E2E_TEST_AUTHENTICATE_USERNAME="Test User"
E2E_TEST_AUTHENTICATE_USER_EMAIL="testuser@mail.com"
E2E_TEST_AUTHENTICATE_USER_PASSWORD="test_Password123"

LOGGER

NEXT_PRIVATE_LOGGER_HONEY_BADGER_API_KEY=
`

Steps to Reproduce

just follow the get started setup

Expected Behavior

Current Behavior

Any button won't trigger any action

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Tested in Brave, Ark, and Edge

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @FilyBox on GitHub (Apr 25, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1761 ### Issue Description Description: I'm currently unable to get the login or signup functionality working. Clicking on "Sign Up" just reloads the page without performing any validation. When trying to create a new user, the "Next" button doesn't do anything and the SignaturePadDialog isn't working either, the SignaturePadDialog is just there empty. It seems like no form actions or button handlers are working at all in the project. I tried adding some console.log statements to debug the process, but none of them are triggered — it looks like no functions are being executed. My environment matches the one described in the "Get Started" section. I'm running the project in a Docker container, and the only difference is that I'm using Neon as my database. However, I don’t believe the issue is related to the database, since no frontend actions are triggered at all. Is there something I might be missing in the setup proccess? my .env file: `# [[AUTH]] NEXTAUTH_SECRET="secret" # [[CRYPTO]] # Application Key for symmetric encryption and decryption # REQUIRED: This should be a random string of at least 32 characters NEXT_PRIVATE_ENCRYPTION_KEY="CAFEBABE" # REQUIRED: This should be a random string of at least 32 characters NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY="DEADBEEF" # [[AUTH OPTIONAL]] # Find documentation on setting up Google OAuth here: # https://docs.documenso.com/developers/self-hosting/setting-up-oauth-providers#google-oauth-gmail NEXT_PRIVATE_GOOGLE_CLIENT_ID="" NEXT_PRIVATE_GOOGLE_CLIENT_SECRET="" NEXT_PRIVATE_OIDC_WELL_KNOWN="" NEXT_PRIVATE_OIDC_CLIENT_ID="" NEXT_PRIVATE_OIDC_CLIENT_SECRET="" NEXT_PRIVATE_OIDC_PROVIDER_LABEL="" NEXT_PRIVATE_OIDC_SKIP_VERIFY="" NEXTAUTH_URL=http://localhost:3000 NEXTAUTH_SECRET=mytestApp POSTGRES_USER="documenso" POSTGRES_PASSWORD="password" POSTGRES_DB="documenso" # [[URLS]] NEXT_PUBLIC_WEBAPP_URL="http://localhost:3000" # URL used by the web app to request itself (e.g. local background jobs) NEXT_PRIVATE_INTERNAL_WEBAPP_URL="http://localhost:3000" # [[DATABASE]]NEXT_PRIVATE_DATABASE_URL="postgres://documenso:password@database:5432/documenso" NEXT_PRIVATE_DATABASE_URL="My Database" # Defines the URL to use for the database when running migrations and other commands that won't work with a connection pool. NEXT_PRIVATE_DIRECT_DATABASE_URL="My Database" # [[SIGNING]] # The transport to use for document signing. Available options: local (default) | gcloud-hsm NEXT_PRIVATE_SIGNING_TRANSPORT="local" # OPTIONAL: The passphrase to use for the local file-based signing transport. NEXT_PRIVATE_SIGNING_PASSPHRASE= # OPTIONAL: The local file path to the .p12 file to use for the local signing transport. NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH= # OPTIONAL: The base64-encoded contents of the .p12 file to use for the local signing transport. NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS= # OPTIONAL: The path to the Google Cloud HSM key to use for the gcloud-hsm signing transport. NEXT_PRIVATE_SIGNING_GCLOUD_HSM_KEY_PATH= # OPTIONAL: The path to the Google Cloud HSM public certificate file to use for the gcloud-hsm signing transport. NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_PATH= # OPTIONAL: The base64-encoded contents of the Google Cloud HSM public certificate file to use for the gcloud-hsm signing transport. NEXT_PRIVATE_SIGNING_GCLOUD_HSM_PUBLIC_CRT_FILE_CONTENTS= # OPTIONAL: The path to the Google Cloud Credentials file to use for the gcloud-hsm signing transport. NEXT_PRIVATE_SIGNING_GCLOUD_APPLICATION_CREDENTIALS_CONTENTS= # [[STORAGE]] # OPTIONAL: Defines the storage transport to use. Available options: database (default) | s3 NEXT_PUBLIC_UPLOAD_TRANSPORT="database" # OPTIONAL: Defines the endpoint to use for the S3 storage transport. Relevant when using third-party S3-compatible providers. NEXT_PRIVATE_UPLOAD_ENDPOINT="http://127.0.0.1:9002" # OPTIONAL: Defines the force path style to use for the S3 storage transport. Relevant when using third-party S3-compatible providers. # This will change it from using virtual hosts <bucket>.domain.com/<path> to fully qualified paths domain.com/<bucket>/<path> NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE="false" # OPTIONAL: Defines the region to use for the S3 storage transport. Defaults to us-east-1. NEXT_PRIVATE_UPLOAD_REGION="unknown" # REQUIRED: Defines the bucket to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_BUCKET="documenso" # OPTIONAL: Defines the access key ID to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID="documenso" # OPTIONAL: Defines the secret access key to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY="password" # [[SMTP]] # OPTIONAL: Defines the transport to use for sending emails. Available options: smtp-auth (default) | smtp-api | mailchannels NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" # OPTIONAL: Defines the host to use for sending emails. NEXT_PRIVATE_SMTP_HOST="127.0.0.1" # OPTIONAL: Defines the port to use for sending emails. NEXT_PRIVATE_SMTP_PORT=2500 # OPTIONAL: Defines the username to use with the SMTP server. NEXT_PRIVATE_SMTP_USERNAME="documenso" # OPTIONAL: Defines the password to use with the SMTP server. NEXT_PRIVATE_SMTP_PASSWORD="password" # OPTIONAL: Defines the API key user to use with the SMTP server. NEXT_PRIVATE_SMTP_APIKEY_USER= # OPTIONAL: Defines the API key to use with the SMTP server. NEXT_PRIVATE_SMTP_APIKEY= # OPTIONAL: Defines whether to force the use of TLS. NEXT_PRIVATE_SMTP_SECURE= # OPTIONAL: if this is true and NEXT_PRIVATE_SMTP_SECURE is false then TLS is not used even if the server supports STARTTLS extension NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS= # REQUIRED: Defines the sender name to use for the from address. NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" # REQUIRED: Defines the email address to use as the from address. NEXT_PRIVATE_SMTP_FROM_ADDRESS="noreply@documenso.com" # OPTIONAL: Defines the service for nodemailer NEXT_PRIVATE_SMTP_SERVICE= # OPTIONAL: The API key to use for Resend.com NEXT_PRIVATE_RESEND_API_KEY= # OPTIONAL: The API key to use for MailChannels. NEXT_PRIVATE_MAILCHANNELS_API_KEY= # OPTIONAL: The endpoint to use for the MailChannels API if using a proxy. NEXT_PRIVATE_MAILCHANNELS_ENDPOINT= # OPTIONAL: The domain to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_DOMAIN= # OPTIONAL: The selector to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_SELECTOR= # OPTIONAL: The private key to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_PRIVATE_KEY= # OPTIONAL: Displays the maximum document upload limit to the user in MBs NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=5 # [[STRIPE]] NEXT_PRIVATE_STRIPE_API_KEY= NEXT_PRIVATE_STRIPE_WEBHOOK_SECRET= # [[BACKGROUND JOBS]] NEXT_PRIVATE_JOBS_PROVIDER="local" NEXT_PRIVATE_INNGEST_EVENT_KEY= # [[FEATURES]] # OPTIONAL: Leave blank to disable PostHog and feature flags. NEXT_PUBLIC_POSTHOG_KEY="" # OPTIONAL: Leave blank to disable billing. NEXT_PUBLIC_FEATURE_BILLING_ENABLED= # OPTIONAL: Leave blank to allow users to signup through /signup page. NEXT_PUBLIC_DISABLE_SIGNUP="false" # [[E2E Tests]] E2E_TEST_AUTHENTICATE_USERNAME="Test User" E2E_TEST_AUTHENTICATE_USER_EMAIL="testuser@mail.com" E2E_TEST_AUTHENTICATE_USER_PASSWORD="test_Password123" # [[LOGGER]] NEXT_PRIVATE_LOGGER_HONEY_BADGER_API_KEY= ` ### Steps to Reproduce just follow the get started setup ### Expected Behavior LogIn or Create a new account ### Current Behavior Any button won't trigger any action ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Tested in Brave, Ark, and Edge ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:20 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 25, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Apr 25, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@divyaswormakai commented on GitHub (May 19, 2025):

I was facing a similar issue recently when trying to run this locally. I managed to bypass this. I think an update to the Readme would be enough for this.
Will create a PR for this soon.
I need to confirm a few things before that.

@divyaswormakai commented on GitHub (May 19, 2025): I was facing a similar issue recently when trying to run this locally. I managed to bypass this. I think an update to the Readme would be enough for this. Will create a PR for this soon. I need to confirm a few things before that.

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 21, 2025):

@FilyBox

Can you run this before your dev server?

 npm run translate:compile

or better still start the dev server with

npm run d

@ephraimduncan commented on GitHub (Aug 21, 2025): @FilyBox Can you run this before your dev server? ``` npm run translate:compile ``` or better still start the dev server with ``` npm run d ```

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@Harishraju04 commented on GitHub (Oct 28, 2025):

1️⃣ Compile Lingui translation files (.po → .mjs)

npx lingui compile

2️⃣ Start the development server

npm run dev

@Harishraju04 commented on GitHub (Oct 28, 2025): # 1️⃣ Compile Lingui translation files (.po → .mjs) `npx lingui compile` # 2️⃣ Start the development server `npm run dev`

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@Harishraju04 commented on GitHub (Oct 29, 2025):

we need to make sure that we compile the lingui before running npm run dev this step is missing in the manual development setup guide. So i will make sure that step is added to the Readme.md file

@Harishraju04 commented on GitHub (Oct 29, 2025): we need to make sure that we compile the lingui before running npm run dev this step is missing in the manual development setup guide. So i will make sure that step is added to the Readme.md file

kerem referenced this issue

2026-02-26 19:31:27 +03:00

[PR #505] [CLOSED] fix: email requesting signature shows "completed document" in preview… #1010

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#505

No description provided.

Rows
Columns