I can't access remotely my postgre database. My fellow is making a QT project that access the database from my web-server. It's very close to the problem from this guy: Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432?
And with some research in google, all solutions point to set the listen_addresses property in postgresql.conf like this:
listen_addresses = '*'
and in pg_hba.conf add this line in the IPV4 connections
host all all 0.0.0.0/0 trust
I've already done it, and also have created an exception in ufw
5432/tcp ALLOW x.x.x.x.x
when x.x.x.x is the ip I want to give access.
I've also tried some variants to the configuration above ,like
listen_addresses = 'localhost, x.x.x.x'
and
host all all x.x.x.x/32 md5
The error message of the linked question happens only when trying to connect locally. That's what ...running on host localhost... means.
When connecting to a remote host, the client doesn't set localhost in the host field, but the IP address or name of the remote machine (well, unless using a SSH tunnel but it's not mentioned here).
Otherwise please indicate the exact connection parameters of the client and the exact error message.
Related
I have a bit of a bizarre problem. I have a Hyper-V VM and I cannot connect to it via IP address on the host computer.
I intend to use it as an SQL server to host a database for a website while I test it, and the first step I can see in this endeavour is to make sure the IP addresses work externally.
Other PCs on the LAN appear to be able to connect just fine via the IP address on Remote Desktop. I cannot do so. I also cannot connect through SQL Management Studio (named pipes or TCP/IP). Although named pipes gives an error relating to being denied access as opposed to IPs which are just not found.
I have tried pinging both ways:
VM => Host : Always gives a "Destination Host Unreachable" error
Host => VM: Always gives a "Request Timed Out" error
As for netstat -a -n, I can see that the VM is listening to 3389 (default Hyper V port, which makes sense).
Regarding Firewalls, all have been turned off on all machines. I can tell that the firewall is not the issue.
If you need any more information to help me to diagnose and treat the problem, please ask me as I would like to get this sorted as quickly as possible.
Thanks a lot in advance.
Which windows server version do you use?
Windows Server 2016 blocks insecure RDP connections (https://support.microsoft.com/en-us/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm).
Since RDP uses CredSSP you have to install the current Windows Patches.
Do you can ping the DNS server by IP address from your VM?
Is ICMP (ICMP = the thing you need for ping) on your host enabled?
Here is a Checklist for ICMP:
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc749323(v=ws.10)
Solved,
Just switched to another physical computer and it was fine.
I recently migrated a site to a new server and am now trying to replace the old domain by the new one using this tool suggested in the wordpress codex.
The SQL instance and the VM are both in the same region and are connected using a cloud sql proxy, however when I try and connect to the database via the searc-replace tool, I get connection refused:
EDIT:
The command used to start the sql proxy is the following:
localhost:/cloudsql/project-name:region:sql-instance-name
It is the same I use in the config file to connect the site to the db.
"Connection Refused" error occurs when an application attempts a TCP connection but there is either no service listening on the target address and port or a firewall rejecting the connection.
First, lets make sure you are connecting on the right port. Run sudo netstat -lntp and look for cloud_sql_proxy. For example you might see
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 71313/cloud_sql_pro
indicating cloud sql is listening on port 3306. If you saw this, you should change the port in your tool to 3306.
If netstat does not show any cloud_sql_proxy line, then it isn't listening on TCP. While TCP isn't always needed for MySQL, it looks like the tool your are using does need it. Make sure you start cloud_sql_proxy with -instances=<INSTANCE_CONNECTION_NAME>=tcp:3306
Second, lets make sure you are connecting on the right address. This should be localhost without :/cloudsql/project-name:region:sql-instance-name after.
If it still doesn't work after those two, use sudo iptables -L to look for firewall rules blocking the traffic. I believe it's unlikely that you have a firewall stopping local traffic, however.
An alternative to using the Cloud SQL Proxy is to connect directly to your instance. To do this:
Find the external IP address of the VM you are running the PHP tool on.
Grant access for that IP address to your SQL instance, with the instructions here
Because MySQL can have different username/password depending on where you connect from, ensure there is a username/password combo for host %. instructions here.
Use the tool, with the username/password from (3), port=3306 and host=the IP address of your SQL instance
When you are done, remove access from the IP address to your Cloud SQL instance.
I apologize for the novice question, but have been struggling on this for many hours. I am running Ubuntu Server on Ubuntu 16.04. I can ssh fine into local host (thus know ssh server is running)
However, when I try to log into my server externally, I get the error message shown below (yes I know port 22 is not secure):
I have enabled port 22 on my /etc/ssh/sshd_config file and allowed the ListenAddress to be everything by leaving it empty (tried with other addresses), and ensured that my iptables are open:
Finally, I am using a static IP address. And ensuring that I am forwarding ports:
I am not including a port triggering as I do not believe that it is necessary?
What do I need to do to expose this server externally and be able to SSH into it? Any help is very much appreciated.
Solved, no responses required. My internal ip address that I had my port forwarding selected for was different than the internal ip address that my computer was on.
I try to host my website for learning, on a CentOS free VPS (no support).
I’m allowed to access Apache service via IPv4 by adding a custom port.
Using the format below, I can access the server with my browser.
e.g. 12345 is my custom port that I created for default port 80:
http://xxx.xxx.xxx.xxx:12345
But I cannot access my hosted website http://mywebsite.com (‘the webpage is not available’).
I’ve created the proper DNS record on my DNS provider, and pointed the domain name to the free VPS server IPv6 address (through CloudFlare).
Note: My ISP doesn't provide IPv6 connection and the IP is not ICMP pingable (I can’t create IPv6 tunnel).
Here is my telnet test communication result (not my real IPv6 address):
[root#myserver ~]# telnet mywebsite.com 80
Trying 1a12:1234:1:1::1:1a23...
Connected to mywebsite.com.
Escape character is '^]'.
Connection closed by foreign host.
[root#myserver ~]#
Why I can’t access my website: http://mywebsite.com ?
Okay.., what fixed it was adding on Cloudflare a 'CNAME' record in addition to the existing 'AAAA' record.
Hope this help someone.
I am using Linux Mint Olivia.
Recently i have installed Wordpress on my local apache server (Lamp).
It was working fine but when i restarted my computer and tried to connect to local server it kept showing following message
Error establishing a database connection
After spending few hours, i have understood that this error occurred because of IP address of my machine changed every time i re-connect to Internet.
bind-address = 192.***.**.**
So whenever i tried to connect web server from browser , i have to edit /etc/mysql/my.cng
files and change
bind-address to new IP address.
How can i fix this problem so that /etc/mysql/my.cng file automatically keep track of new IP address.
Thanks
Don't bind the LAN ip address to your mysql server setup. Comment that line out. This way, you can setup your wordpress to connect to mysql server "localhost" or "127.0.0.1" local loopback address.
Or
Fix your network adapter to one of the 192.xxx ip you get from DHCP, so that it doesn't change on reconnect.