I am trying to connect to CloudSQL DB from Informatica server which is inside a corporate proxy. I have got the Public IP of the server and added to authorized networks.
But unable to connect to server still and tried CIDR notation to add whole all IP's ..*.0/24.
Is there anyway in CloudSQL to get connections which are getting refused, so that it can be added to Authorized networks.
Did you assign an public IP to your instance? This is necessary to be able to connect over the internet.
Can you create a new GCE VM to connect?
create VM with ubuntu image
run sudo apt-get install mysql-client
whitelist the VM's IP address in Cloud SQL
use the mysql client on VM to connect
To answer your question, "Is there anyway in Cloud SQL to get connections which are getting refused, so that it can be added to Authorized networks."
You can whitelist everything with "0.0.0.0/0" and "::/0" (IPv6).
There is no way to see a log of the IP addresses of rejected connections. The IP address you should whitelist is usually what you see at ip4.me.
If whitelisting is the problem the error message should be "Lost connection to MySQL server at 'reading initial communication packet'". If you get a different error message you may be connecting to the wrong IP address, may not have an IP address assigned to your instance, or might have a corporate firewall stopping outbound MySQL connections (port 3306).
Related
When I'm trying to connect my ClickHouse instance on Alibaba Cloud with https protocol from my Mac, and this is the response error:
Failed to connect to cc-xxxx.germany.ads.aliyuncs.com port 8443: Operation timed out
enter image description here
curl --cacert ./Downloads/ClickHouse-CA-Chain.pem https://cc-clickhouseinstance.connection.string.ads.aliyuncs.com:8443/ping
I have tried ping, and it shows ok, so what the problem would be?
How to connect ApsaraDB for ClickHouse instance on Alibaba Cloud using https?
Maybe you should check your instance security group, be sure the public IP of your PC is on the allow list.
If you don't know how to get your public IP, check below.
https://ip.taobao.com/ipSearch
Or you can switch to connect from ECS instances and put public IP or intranet IP on the list. Just like this👇
Data Security Rules Configuration Example
[Reference]
https://www.alibabacloud.com/help/doc-detail/393349.htm
In my Azure portal I created the resource "Azure Database for PostgreSQL server". I set up the firewall to enable two Virtual Networks (in order to allow the correct functioning of two applications) and the IP address of my local computer (in order to be able to work on the database using DBeaver as client). This has worked for several months although, since I have a dynamic IP address, I often have to change the enabled address. Now I'm trying to update it but, when I try to connect to the database via DBeaver, I get the following error:
FATAL: no pg_hba.conf entry for host "XX.XX.XX.XX", user "myuser", database "mydatabase", SSL on
where "XX.XX.XX.XX" is exactly the IP address I have enabled in Azure.
I tried to install a second Client (pgAdmin) but I get the same error. Also, since my applications that use the database seem to work properly, I tried to verify the connection data that I use in DBeaver (host, database, user, password) but they are all correct.
In Azure, in the "Connection security" tab of my database (see image below) I read the following warning:
Some network environments may not report the actual public-facing IP address needed to access your server. Contact your network administrator if adding your IP address does not allow access to your server.
So changing the IP address has no effect? How can I solve the problem?
I solved the problem by restarting the database: https://learn.microsoft.com/en-us/azure/postgresql/howto-restart-server-portal
In the Azure Portal change require_secure_transport from server parameters to OFF.
make ssl connection non mandatory in server parameters for postgres service in azure, its dynamic parameter so no postgres service restart not required
or fix/configure application to use secure(ssl) connections only
I created a virtual machine and install our own copy of MS SQL2016. I can connect fine from the VM but when I try to connect from outside (my office) it say that it cannot find the network instance. I have tried the Server name (Mapped in host file) the DNS name connected to the public IP and even the public IP. I have enabled the TCP/IP protocol and set the port (1433), set up a Windows firewall rule, set up incoming rule in Network security group, read articles and tried many things but still same message .

Anyone have an idea?
I am trying to mirror a on premise SQL database to Azure ARM VMs running SQL server. One for the mirror and one for the witness. I have setup the mirroring end points on the servers. However, I am getting an error to the effect that the mirror server can not be reached.
Reading through the net pages, I tested the port using telnet. I am able to telnet to the mirroring port on my local server from the Azure VM but unable to telnet from the local server to the VMs.
I am able to telnet on the mirroring port between the VMs using the Private IP Address but unable to do so using the Public IP address.
I have added the port to the Security group being used by these VMs to allow inbound connections as well as outbound connections.
I have tested that the server is listening on ip 0.0.0.0 and my mirroring port.
Any help would be very much appreciated.
For whatever its worth, I was setting the Inbound connections source port range as the port I was going to use for mirroring. I changed this to "*" and it started working.
I have created database and user and give all the privilege to the user.When i give the IP as Database host.It will show the following errors.Giving hostname as localhost it will work fine.
I am using phpmyadmin 3.3.2...
The error message is given below.
Failed to connect to your MySQL database server. MySQL reports the following message: Can't connect to MySQL server on '192.168.85.10' (111)
It seems that the IP address you use is your "external" IP and not the IP localhost would resolve to, which is most of the time your loopback: 127.0.0.1.
So if you are trying to connect from the same computer as the database is running you should use 127.0.0.1 as the IP address.
If you are trying to connect to your database from another computer on the network, you should enable MySQL remote access in your my.conf (MySQL config file). Because by default MySQL disables remote incoming connections.
You do this by setting the "bind-address" line to your real (external) server IP as such:
bind-address = 192.168.xx.xx (assuming its on your local network)
Or put the bind-address in comment.
Also make sure that the skip-networking option is commented as such:
#skip-networking
And then restart your MySQL server.
Now also make sure that your MySQL users are also allowed to connect from locations other then "#localhost".
I hope this helps!
Cheers,
Timusan