Are you using the private network to connect to the database? if not, please do.

I was not. Now, when I do try to change my 'HOST' to 'postgres.railway.internal' as the settings specify, I am now getting a host error. My settings are set up as follows:

'ENGINE': 'django.db.backends.postgresql',
'NAME': 'railway',
'USER': 'postgres',
'PASSWORD': '***********************',
'HOST': 'postgres.railway.internal',
'PORT': '25924',

Please provide the error.

Are you on the V2 runtime? if not, try switching to it.

This is the local error when I try changing my HOST settings to 'postgres.railway.internal' :

django.db.utils.OperationalError: could not translate host name "postgres.railway.internal" to address: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

I am on V2 runtime as well.

You can not connect to the private domain locally, please push the changes and see if your app once running on Railway can connect to the database now.

I just pushed it and got a different error in production:

could not translate host name "postgres.railway.internal" to address: Name or service not known

Is your database in the same project as your django service?

No. The Django project is hosted on pythonanywhere. The postgres database is all that is in Railway.

Your django app and database would need to be in the same project in order to access the database over the private network, as it is now you are subjecting yourself to egress fees and increased latency.

Okay, thanks.