I have a site running on an Azure App Service. It connects to a MySQL DB on Google CloudSQL.
All of a sudden I am getting an error when I hit a page on my site. The error is:
Configuration Error - Reading from the stream has failed.
I know this is related to MySQL and an attempt to read from the DB.
The DB itself is fine - minimal connections, no stress.
The site runs fine from my local VS connecting to said database.
This makes me think I have hit some kind of 'outbound' connection limit on Azure. Can anyone confirm?
The Azure site is up and running but as soon as it tries to connect to the DB it falls over.
Thanks for any help you can give!
Update - IP Changed??
It appears that the App Service outbound IP addresses changed at some point yesterday so our external MySQL DB started blocking the connection attempts. Has anyone experienced this? Every single outbound IP changed. Nothing has been changed on the setup of the app (no scaling etc)
Related
I deploy a node + sql application I made testes running the node app in my laptop using mysql database provided by google and the application was working fine (I needed to allow my ip address to connect) but when I deployed the application I started to receive timeout errors in my app. I solved the problem allowing any ip address to connect in my google cloud mysql instance but I not happy with this solution. Anybody can help to allow just the production node app server ip?
Thanks in advance.
If you want your API key to only be accessed from a certain IP, you can restrict it in the Developers Console.
I'm trying to establish a basic mysql connection from a google compute engine instance in one project to a google cloud sql instance (2nd generation) in a different project.
I've done this many times before without any problem. You simply add the ip address of the google compute instance to the list of authorized networks for the google cloud sql instance. This has always worked in the past but it is not working now.
The only thing that I can think of which is different about this situation is that I've recently been experimenting with using the cloudsql-proxy to establish a connection from a different gce instance to the same google cloud sql instance. Could this be the problem? Perhaps the google cloud sql instance is getting confused by having to support both connection mechanisms?
I just need the connection to work. Is there a work-around?
There isn't a problem using both modes of connectivity simultaneously.
The only thing I can think of is that you are accidentally using an ephemeral IP addresses for your VMs instead of static, which means the VM may have a different IP address than you expect (after a restart, for example).
If that's not the case, please send a mail to cloud-sql#google.com with a little bit more information (project and database name, project/name/ip of your VM) so that we can figure out what's going on in the backend.
My app seems to run fine sometimes, and other times it says it cannot connect to any of the MySQL servers.
I started out with the MySQL server being hosted in azure as well, but I moved it external due to connectivity issues.
I finally moved the ASP.Net app to a real VM instead of being hosted as a website. I tested a manual connection to the MySQL server when it became unresponsive and it failed as well. I then did a trace route to the server and it failed as well.
Is this a known issue? Is this a duplicate of: Classic ASP site on Azure web site, remote mysql database
I am currently running a virtualized environment for my web and db server. When I access the web server or the MySQL server individually, they are both fast. I also have websites running on the web server that do not require the db server and those all load quickly. However, when I access my hosted website that requires the web server to call from the db server, there is about a 5-7 second latency for every page load. This has been confirmed with both a very simple site and with a Word Press setup as well. Here is the config:
Web server - CentOS 6.5, Apache 2.2.15
DB server - CentOS 6.5, MySQL 5.1.73
My question is, are the servers continuously authenticating with one another (and thus causing latency) on every single db call? If that is the case, does anyone know how to permanently authenticate between the two?
I might be way off on this assumption and authentication could have nothing to do with it. I am completely open to any and all ideas at this point. Thank you very much.
V/R,
Tony
To me it seems to be a network issue.
and obviously the db-server will need authentication every time there is a hit.
I have a number of apps running on Dreamhost and am creating a small app I will use locally to present reports on information stored in various databases. I do not want to host this reporting tool online so I need the app to connect to the remote MySQL server from my machine.
Codeigniter has been giving me an error all afternoon that it can't connect to the remote server, I'm guessing this is down to Dreamhosts security on remote access. I don't have a dedicated IP address so it's not ideal to set on the user account to allow external access. I've tried exploring an IP tracking solution such as No-IP, however I'm not sure if I've configured it properly, or if it'll even the service is capable of allowing my app to access the remote MySQL server when ever it needs.
Does anyone know how to get these working correctly, or am I on the right track??