I am running sqlworkbench/j on ubuntu. I am not able to connect to the database through proxy server. How to setup the proxy setting of the Amazon redshift jdbc driver.
Did you allow inbound traffic from the proxy to redshift? Normally you would provide access using a security group with an inbound TCP Rule from a given IP on Port 5438 (default Redshift port). You would have to find out and enter your proxy's IP adress.
Related
When creating MySQL Flexible Server (DBaaS) on Azure that is not publicly accessible a private DNS zone is being created making that MySQL Flexible Server accessible via a hostname. While debugging why I'm able to connect to MySQL Flexible Server from a jumpbox VM, but not when using Virtual Network Gateway - Point to site connection - OpenVPN, I've discovered that the DNS zone has a private IP:
I'm able to connect to MySQL Server using this IP from both jumpbox VM and from local computer using point-to-site OpenVPN.
What is that IP? Since connecting to MySQL via IP is easier than setting up Private DNS zone and connecting via hostname, why this IP is not documented? Can we use it in production?
Wondering if you have custom DNS forwarder setup as shared below
https://learn.microsoft.com/azure/mysql/flexible-server/concepts-networking-vnet#connecting-from-on-premises-to-flexible-server-in-virtual-network-using-expressroute-or-vpn
I have created a CloudSQL instance which was part of a VPC I have created.
I'm able to connect to this CloudSQL using CloudSQL Proxy service. But I'm unable to connect to this instance using public IP of the instance though I added the firewall rule to this VPC.
The error I'm getting:
Unable to connect to host <public-ip-of-cloudsql>, or the request timed out.
Be sure that the address is correct and that you have the necessary privileges, or try increasing the connection timeout (currently 10 seconds).
MySQL said:
Can't connect to MySQL server on '<public-ip-of-cloudsql>' (4)
Following is the firewall rule I added and provided my home IP address in the blocked out area.
Please let me know if I'm missing something. I can provide more details if needed.
These are the steps you should follow in order to connect to Cloud SQL using the public IP:
Created a Cloud SQL instance, including configuring the default user.
Assuming you use a local client:
2.Install the client.
3.Configure access to your Cloud SQL instance.
4.Connect to your Cloud SQL instance.
You can find a detailed explanation here: Connecting MySQL client using public IP
If you are using the Cloud SQL proxy to connect via public ip, it requires port 3307 to be open to the address.
If you aren't using the Cloud SQL proxy to connect via public ip, you need to authorize your external IP.
I was able to connect CloudSQL which is part of a VPC by just adding the client IP address as Authorized networks.
It's weird, I tried many times before but couldn't succeed. It is working now.
Thanks, guys for answers.
I want to connect externally to my Redshift cluster (VPC, NOT classic) using aginity workbench. Hence I added my public ip address to the ec2 inbound rules, but I get a connection timeout.
When I allow all traffic to the inbound rules (0.0.0.0/0) it is possible to connect.Off course this is not a preferred solution because of security.
Does anybody have an idea why/where it is failing with my public ip (grabbed from whatismyipaddress.com)?
I am trying to connect to an AWS postgresql RDS via psycopg2. When I set my inbound rules on my security group to accept all traffic via postgresql on port 5432, I am able to connect.
However, when I constrain my inbound rule for postgresql on this port to accept traffic only from my client IP, I cannot connect and it times out. I get the error:
psycopg2.OperationalError: could not connect to server: Connection
timed out Is the server running on host "[hostname]" ([some IP
address]) and accepting TCP/IP connections on port 5432?
Thanks for any advice. I have tried configuring the inbound rules on my security group for my RDS instance to accept my client IP, my ec2 Instance private IP, and the IP address given in the error above, but no joy. Only accepting all traffic works. Any advice on what I'm doing wrong?
Thanks!
Identify your IP from this link: https://www.whatismyip.com/. In the security groups, enable inbound rule to this IP followed by /32.
Example, if your IP from the above link comes as 192.168.0.25, then in security groups, add 192.168.0.25/32 as the source.
In my case, I found the answer was to configure an elastic IP so that it would have a constant value that could be accepted by my RDS security group. Perhaps other posters took it for granted that I had done so; I didn't know that was was part of the solution. Thanks for everyone's advice.
I am able to connect Cloud SQL using SQL Yog using my internet data card as it provides a unique IP address for the handshake process . But from office i cannot connect as it has a firewall. And when the IP address i receive is of my firewall instead of my host. Is there a better way to connect Cloud Sql from office where firewall IP restricts the handshake process
I don't know what SQL Yog is, but one other option is to create a Google Compute Engine instance. You can then connect from your workstation to the GCE instance, and then connect to Cloud SQL from within that instance.