You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
So I'm working on my 'Alpha' project with Django on the App Engine, with this skeleton starting point, and I was finally about to connect and migrate the database over to the cloud to test it. But even though I was able to do it in the very same project about 10 days ago, now I get the error message
django.db.utils.OperationalError: (2003, "Can't connect to MySQL server on '207.223.160.200' (10060)")
And I'm sure I have changed nothing in regards to the database connection, except for updating the requested IP address.
Just to see if I have done something weird in the Alpha project, I jumped back to the prototype, which I know I was able to connect and sync with no problems about a month back. But now I get the same error message on that project as well.
I also did a manual test as such via the python manage.py shell:
So has anything changed in respect to connecting to the Cloud SQL database?
The text was updated successfully, but these errors were encountered:
nitrax92
changed the title
Cant connect to the MySQL server in 'Assigned IP adress' anymore - Has anything changed?
Cloud SQL - Cant connect to the MySQL server in 'Assigned IP adress' anymore - Has anything changed?
Apr 13, 2016
My bad, it works fine now - and it was not an issue with this skeleton, or even Django, but rather Cloud SQL had some issues with instances which had IP addresses 207.x.x.x
So I'm working on my 'Alpha' project with Django on the App Engine, with this skeleton starting point, and I was finally about to connect and migrate the database over to the cloud to test it. But even though I was able to do it in the very same project about 10 days ago, now I get the error message
django.db.utils.OperationalError: (2003, "Can't connect to MySQL server on '207.223.160.200' (10060)")
And I'm sure I have changed nothing in regards to the database connection, except for updating the requested IP address.
Just to see if I have done something weird in the Alpha project, I jumped back to the prototype, which I know I was able to connect and sync with no problems about a month back. But now I get the same error message on that project as well.
I also did a manual test as such via the python manage.py shell:
But the same error message returned.
So has anything changed in respect to connecting to the Cloud SQL database?
The text was updated successfully, but these errors were encountered: