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 }}
Repository navigation
App Engine and Cloud SQL - connection lost issue #163
I have forked the appengine/cloudsql project and deployed to google cloud however I am getting follow error Connection lost: The server closed the connection. each time I deploy the app. I am able to run application on my local machine using cloud_sql_proxy without any problem so it seems the issue is somewhere between app engine and cloud sql as Mysql connection is always dropping..
In app.yaml I am using follow MYSQL_SOCKET_PATH: /cloudsql/[YOUR_PROJECT_ID]:[YOUR_REGION]:[YOUR_INSTANCE_NAME]
Are there any changes in configuration or doc that I am missing?
The Connection lost: The server closed the connection error means that at least credentials are correct otherwise I would see ENOENT or access denied error message so there might be something wrong with socket.
Assuming you've made no alterations to the sample and you've already successfully connected to your Cloud SQL instance from your local computer to verify that your test1 database exists, then I don't know what the problem could be. I'll have to open an issue.
Activity
jmdobry commentedon Aug 10, 2016
Can you post the exact contents of
app.yaml?martinmicunda commentedon Aug 10, 2016
The Connection lost: The server closed the connection error means that at least credentials are correct otherwise I would see ENOENT or access denied error message so there might be something wrong with socket.
jmdobry commentedon Aug 10, 2016
You need to replace all of the variables with your actual values, e.g.
[YOUR_PROJECT_ID]=>my-project,[YOUR_USER]=>my-user-name, etc.martinmicunda commentedon Aug 10, 2016
I know :) so let's assume
[YOUR_PROJECT_ID]is name of your project id that you can get from Cloud SQL console thenapp.yamllooks like this:jmdobry commentedon Aug 10, 2016
I just successfully deployed the Cloud SQL sample to https://sql-dot-nodejs-docs-samples.appspot.com/ using:
Assuming you've made no alterations to the sample and you've already successfully connected to your Cloud SQL instance from your local computer to verify that your
test1database exists, then I don't know what the problem could be. I'll have to open an issue.martinmicunda commentedon Aug 10, 2016
I found where the problem was. I had to enable the
Cloud SQL Administration APIand everything works fine now. Thanks for help ;)jmdobry commentedon Aug 11, 2016
Ah, I didn't think of that.
chore: release 2.3.1 (#163)
test: fix failing tests due to leaks (#163)
chore: release 2.3.1 (#163)
chore: release 2.3.1 (#163)
chore: release 2.3.1 (#163)
chore: release 2.3.1 (#163)
chore: release 2.3.1 (#163)
test: fix failing tests due to leaks (#163)
chore(deps): lock file maintenance (#163)
chore(deps): lock file maintenance (#163)
chore(deps): lock file maintenance (#163)
chore: release 2.3.1 (#163)
docs: add create agent code sample (#163)
chore: release 3.2.2 (#163)
chore: release 3.2.2 (#163)
chore: release 3.2.2 (#163)
docs: add create agent code sample (#163)
chore: release 2.1.0 (#160)
chore: release 2.1.0 (#160)
migrate code from googleapis/nodejs-dialogflow-cx (#2854)