SSL, Certificate, and Reverse Proxy Errors | Appsmith
https://docs.appsmith.com/help-and-support/troubleshooting-guide/ssl-certificate-errors • 53 KB fetched Open original page
SSL, Certificate, and Reverse Proxy Errors | Appsmith
Skip to main content
Ask AI
Search
Ask Appsmith AI Submit message
Examples How do I install Appsmith using Docker? How do I connect to my local PostgreSQL database? How do I pass inputs from a widget to a query? How do I trigger multiple queries conditionally? How do I fix the error: This value does not evaluate to type Array<Object>?
Search
Try Appsmith
* Get Started
* Introduction
* Build Your First App
* Self Hosting
* New Installation Guides
* Manage Installation
* Upgrade Installation Guides
* Concepts
* Connect Data
* Overview
* How-to Guides
* Reference
* Datasources
* Query Settings
* Concepts
* Build Apps
* Overview
* Quickstart
* How-to Guides
* Reference
* Widgets
* Accessibility
* Theme
* Sample Apps
* Write Code
* Overview
* How-to Guides
* Reference
* Global Objects
* Global Functions
* JS Libraries
* Fetch API
* Data Transformation
* JavaScript Settings
* Concepts
* Best Practices
* Manage Apps and Users
* Authentication
* Granular Access Control
* Versioning with Git
* Setup SCIM Provisioning
* Embed Appsmith
* Migrate Applications
* Audit Logs
* Branding
* External Client Portal
* Packages
* Overview
* Tutorial
* How-to Guides
* Reference
* Package Version Control
* GIT Apps with Packages Best Practices
* Code Packages
* UI Packages
* Workflows
* Overview
* Tutorial
* How-to Guides
* Reference
* Workflow Triggers
* Workflow Queries
* Workflow Functions
* Pass Parameters to Workflows
* Run History
* Troubleshooting
* Overview
* Self-hosting Errors
* MongoDB Startup Error Post Migration to Version 5
* Schema Mismatch Error
* Kubernetes Helm Chart 3.0.4 Upgrade Error
* Recover admin access when you don't know the admin email
* Backup and Restore Errors
* License and Activation Errors
* Verify connectivity to cs.appsmith.com
* SSO and Authentication Errors
* User Management and Permissions Errors
* SSL, Certificate, and Reverse Proxy Errors
* Email and SMTP Errors
* Performance and Resource Errors
* Monitoring and Audit Log Errors
* Upgrade and Migration Errors
* Application Errors
* Product
* FAQ
* Security
* Telemetry
* Support at Appsmith
* Privacy Policy
* Release Notes
* Contribute
© 2026 Appsmith, Inc.
*
* Troubleshooting
* Self-hosting Errors
* SSL, Certificate, and Reverse Proxy Errors
On this page
SSL, Certificate, and Reverse Proxy Errors
This page shows how to resolve common SSL, certificate, and reverse proxy errors on self-hosted Appsmith.
Custom CA or self-signed certificate not trusted
PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Cause
Appsmith does not trust the certificate presented by an internal endpoint or by a firewall/proxy that performs SSL decryption. This happens when the signing CA root certificate is not in Appsmith's trust store.
Solution
* Add the custom CA root certificate to the ca-certs folder. For Docker, place it in stacks/ca-certs ; for Kubernetes add it via values.yaml . If the file has a .pem extension, rename it to .crt . See Custom CA Root Certificate .
* Add the correct issuing CA certificate, not the server's own self-signed certificate. You can extract the chain with openssl s_client -connect <host>:443 -showcerts and identify the issuing CA cert.
* Restart Appsmith after adding the certificate so it applies the change on startup.
* Verify the bundle works before relying on it: curl --cacert <bundle>.crt https://<your-appsmith-host> .
Self-signed certificate on a datasource or API action
Cause
A self-signed certificate used by a specific datasource or API endpoint is not a CA-signed certificate, so adding it to the ca-certs folder is not the intended fix and will not work.
Solution
* For a self-signed certificate, attach the certificate directly to the API action in the UI rather than placing it in ca-certs .
* Only use the ca-certs folder when the certificate is signed by a custom Certificate Authority (CA). In that case add the custom CA's certificate, not the leaf/self-signed certificate.
External MongoDB TLS connection fails
Client network socket disconnected before secure TLS connection was established
Cause
Appsmith cannot complete the TLS handshake with an external MongoDB. This typically occurs when the replica set is not initialized or the connecting user lacks the required roles, rather than a certificate problem in Appsmith itself.
Solution
* Run rs.initiate() as an admin user inside your MongoDB cluster to start the replica set configuration, which Appsmith requires for an external MongoDB.
* Ensure the user Appsmith connects with has the readWrite and clusterMonitor roles assigned.
* Test connectivity from a standalone instance in the same network to confirm MongoDB is reachable.
Certificate renewal not reflected when SSL terminates at a load balancer
Cause
When SSL termination happens at a load balancer, the application servers communicate over plain HTTP and never see or validate the external SSL certificate. Updating ca-certs on the application servers therefore has no effect on the public certificate.
Solution
* If SSL terminates at the load balancer, update the certificate there; there is no need to update ca-certs on the application servers.
* Only update ca-certs on the application servers if Appsmith makes outbound HTTPS calls to other services, if load-balancer-to-application traffic is encrypted, or if mutual TLS (mTLS) is in use.
Custom domain causes redirect loops or 401 errors behind a reverse proxy
Cause
When NGINX, ingress-nginx, or another load balancer sits in front of the Appsmith container and also handles SSL termination, setting APPSMITH_CUSTOM_DOMAIN conflicts with the proxy and causes bad redirects, infinite redirect loops, 401 errors, or NULL domain errors.
Solution
* If you have NGINX, ingress-nginx, or any load balancer in front of the Appsmith container, remove the APPSMITH_CUSTOM_DOMAIN environment variable from your docker.env / values to avoid bad redirects and 401 errors.
* Avoid using the latest image tag; pin a concrete version so multiple Appsmith versions don't run in the cluster simultaneously.
Setting up a custom domain with SSL
Cause
A custom domain with HTTPS is not reachable because prerequisites such as open ports are not met, or because custom domains are being attempted on Appsmith Cloud (not supported).
Solution
* Custom domains and SSL are only available on self-hosted Appsmith; this cannot be configured on Appsmith Cloud.
* Ensure ports 80 and 443 are open and accessible (or your custom ports if used). See Custom Domain and SSL .
* Appsmith can provision a certificate automatically through Let's Encrypt when the domain is set; access the instance via HTTPS on port 443 after restart.
Adding the HTTP Strict-Transport-Security (HSTS) header
Cause
Appsmith does not provide a built-in option to add the Strict-Transport-Security (HSTS) header to all responses.
Solution
* Adding the HSTS header to all Appsmith responses is not available directly in Appsmith. Configure it on your gateway/reverse proxy instead (for example, a header-setting policy on the API gateway in front of Appsmith).
Was this page helpful?
Edit this page
Previous
User Management and Permissions Errors
Next
Email and SMTP Errors
* Custom CA or self-signed certificate not trusted
* Self-signed certificate on a datasource or API action
* External MongoDB TLS connection fails
* Certificate renewal not reflected when SSL terminates at a load balancer
* Custom domain causes redirect loops or 401 errors behind a reverse proxy
* Setting up a custom domain with SSL
* Adding the HTTP Strict-Transport-Security (HSTS) header
Links found on this page
- Skip to main content [direct]
- Try Appsmith [direct]
- Get Started [direct]
- Build Your First App [direct]
- Self Hosting [direct]
- New Installation Guides [direct]
- Manage Installation [direct]
- Upgrade Installation Guides [direct]
- Concepts [direct]
- Connect Data [direct]
- How-to Guides [direct]
- Reference [direct]
- Query Settings [direct]
- Concepts [direct]
- Build Apps [direct]
- Quickstart [direct]
- How-to Guides [direct]
- Reference [direct]
- Widgets [direct]
- Accessibility [direct]
- Theme [direct]
- Sample Apps [direct]
- Write Code [direct]
- How-to Guides [direct]
- Reference [direct]
- Global Objects [direct]
- Global Functions [direct]
- JS Libraries [direct]
- Fetch API [direct]
- Data Transformation [direct]
- JavaScript Settings [direct]
- Concepts [direct]
- Best Practices [direct]
- Manage Apps and Users [direct]
- Granular Access Control [direct]
- Versioning with Git [direct]
- Setup SCIM Provisioning [direct]
- Embed Appsmith [direct]
- Migrate Applications [direct]
- Audit Logs [direct]
- Branding [direct]
- External Client Portal [direct]
- Packages [direct]
- Tutorial [direct]
- How-to Guides [direct]
- Reference [direct]
- GIT Apps with Packages Best Practices [direct]
- Code Packages [direct]
- UI Packages [direct]
- Workflows [direct]
- Tutorial [direct]
- How-to Guides [direct]
- Reference [direct]
- Workflow Queries [direct]
- Workflow Functions [direct]
- Pass Parameters to Workflows [direct]
- Run History [direct]
- Troubleshooting [direct]
- Self-hosting Errors [direct]
- MongoDB Startup Error Post Migration to Version 5 [direct]
- Schema Mismatch Error [direct]
- Kubernetes Helm Chart 3.0.4 Upgrade Error [direct]
- Recover admin access when you don't know the admin email [direct]
- Backup and Restore Errors [direct]
- License and Activation Errors [direct]
- Verify connectivity to cs.appsmith.com [direct]
- SSO and Authentication Errors [direct]
- User Management and Permissions Errors [direct]
- Email and SMTP Errors [direct]
- Performance and Resource Errors [direct]
- Monitoring and Audit Log Errors [direct]
- Upgrade and Migration Errors [direct]
- Application Errors [direct]
- Product [direct]
- Security [direct]
- Telemetry [direct]
- Support at Appsmith [direct]
- Privacy Policy [direct]
- Release Notes [direct]
- Contribute [direct]
|
|