Whenever I try to make Django migrations I get this error below what is causing it? I can run makemigrations successfully, and now django migrate command. Also, ever since I connected to Django app, database and buckets, I can no longer run the Django server locally on my computer.
django.db.utils.OperationalError: connection to server at “app-ffb0c792-66af-4849-9524-05a756f81199-do-user-14954907-0.c.db.ondigitalocean.com” (64.23.139.202), port 25060 failed: Operation timed out Is the server running on that host and accepting TCP/IP connections?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hello Chris,
The issue you’re encountering with your Django application’s connection to the DigitalOcean managed database is likely related to the configuration of trusted sources in DigitalOcean. This is a common setup detail that can lead to the type of timeout error you’re experiencing. Here’s how you can address it:
Check the Trusted Sources Setting:
Add Your IP to Trusted Sources:
Consider Connection Pooling:
By ensuring your local environment and application are listed as trusted sources in your DigitalOcean database settings, you should be able to resolve the connection timeout issue.
Let me know how it goes!
Best,
Bobby
Heya @chrismlalazi,
That’s really weird, can you please make sure you’ve followed the directions here to the letter :
https://docs.digitalocean.com/developer-center/deploy-a-django-app-on-app-platform/
See if there is anything you missed.
As for the local environment, it shouldn’t be in anyway related to your Djago App Platform can you confirm how exactly is it not working.