Connections are how applications and databases can communicate. There are two main ways this can be achieved:
- An external connection makes an internet round-trip, so it is much slower than internal communication. We recommend external connections if you are hosting only your database with us but not your front end. For applications, external connections can be made through the web server, as you would expect.
- An internal connection stays within our network and is thus much faster and more secure. We recommend this method if you host both your front-end and your database with Application Hosting and Database Hosting.
Add an Internal Connection
You can add internal connections from an application’s Settings page or a database’s Overview page. It doesn’t matter where you start the process; the result will be the same.
To add a connection from an application to a database, go to Applications > appname > Settings > in the Internal connections section, click Add connection, and select the database you’d like to create the internal connection to.
We can automatically populate an application’s environment variables from the database connection details. Do not copy and paste the internal connection details into environment variables. Click Add connection or Add application and select the Add environment variables… checkbox. This will automatically populate the environment variables from the database you’re connecting to.
Some applications may expect environment variables (keys) with different names. You can edit the names in the list before adding the connection or edit them later on the application’s Environment variables page.
Internal Connections and the Build Process
Internal connections are only available during runtime; they are not available during the build process.
If your application tries to connect to a database using an internal connection during the build process, this causes an error that says the database is not running, which makes the build fail. This is expected because the internal connection is not live during the build; it can only be used during runtime.
There are a couple of ways to work around this.
Option 1: Move the logic that connects to the database from the application’s build command to the start command. For example: if you have a command like
prisma migrate in the build process and move that command to the start command, your application will only access the database during runtime, and the build will be successful.
Option 2: Add separate environment variables as needed for the database connection, one available for the build process, and the other only for runtime. The keys can be the same (e.g.
DB_CONNECTION_URL) as long as one is only available during the build process and the other is only available during runtime. Use the database’s External connection details (Databases > dbname > Overview > External connections) for the values of any variables to be used in the build process.
The port for internal connections to an application is 8080, and the port for internal connections to a database is 3306. The ports for these internal connections cannot be changed.
For applications, Kinsta automatically sets the
PORT environment variable. You do not need to define it yourself or hard-code it into the application. When an application is deployed, it is reachable on the internet on ports 80 and 443, and we route those ports to the container on port 8080.
Remove an Internal Connection
If you need to remove a connection, go to the Application’s Settings page, and under Internal connections, click the delete (trash can) icon.
In the Remove connection modal/pop-up, click Remove connection to confirm and remove the connection between the application and database.