Category: Installation
Updated

This solution is summarized from an archived support forum post. This information may have changed. If you notice an error, please let us know in Discord.

400 bad request error coming while trying to self host

Issue

I am new to appsmith and trying to self-host it using Docker and Caddy as a reverse-proxy. I set the custom domain and copied the certificates to the SSL directory. However, when I access my public URL, I get a 400 Bad Request error saying that the plain HTTP request was sent to the HTTPS port. I followed a guide to set it up but I'm stuck and need help.

Resolution

The user was trying to self-host Appsmith using Docker and Caddy as a reverse-proxy. They set the APPSMITH_CUSTOM_DOMAIN to their custom domain in the docker.env file and copied the certificates obtained by Caddy to the /stacks/ssl directory. They also set the port configuration as 6969:443 in the docker-compose.yml file. However, when they hit their public URL, they received a 400 Bad Request error saying that the plain HTTP request was sent to HTTPS port.

The solution was to make sure to hit the public URL with https:// instead of http://. After doing so, the error was resolved and Appsmith was successfully accessed through the custom domain.