Bom dia; Eu acrescentei a seguinte linha no arquivo de configuração /etc/postgresql/9.6/main/postgresql.conf
listen_addresses = '*' Depois disso a mensagem de erro mudou para: An error has ocorred Error connecting to server: FATAL: nenhuma entrada no pg_hba.conf para a máquina 192.168.0.25, usuário "postgres" banco de dados "postgres", SSL habilitado. FATAL: nenhuma entrada no pg_hba.conf para a máquina 192.168.0.25, usuário "postgres" banco de dados "postgres", SSL desahabilitado. Em 27/04/2019 12:52, China escreveu: O pgadmin tem um arquivo próprio de configuração, vc ajustou ele? No seu hba.conf tem de ajustar o range, tá com só o localhost, por isso só funciona de dentro do servidor. No trecho abaixo vc tem de declarar seu range de IP. Ajuste os arquivos, reinicie os serviços e testa, mande retorno pra lista # IPv4 local connections: host all all 127.0.0.1/32<http://127.0.0.1/32> md5 Em sáb, 27 de abr de 2019 11:55, Vitor Hugo <vitorhug...@hotmail.com<mailto:vitorhug...@hotmail.com>> escreveu: estou tentando me conectar ao servidor postgresql no debian 9 fiz a instalação esta funcionando dentro do debian quando acesso o servidor via ssh ele conecta e funciona porem quando entro em outra maquina para fazer a conexão com o servidor debian/postgre com o pgadmin 4 ele da a mensagem de erro abaixo: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "192.168.0.27" and accepting TCP/IP connections on port 5432? Tentei criar outro usuário e outra senha porem o problema continua. segue abaixo a configuração do meu pg_hba.conf root@debian:/etc/postgresql/9.6/main#<mailto:root@debian:/etc/postgresql/9.6/main#> cat pg_hba.conf # PostgreSQL Client Authentication Configuration File # =================================================== # # Refer to the "Client Authentication" section in the PostgreSQL # documentation for a complete description of this file. A short # synopsis follows. # # This file controls: which hosts are allowed to connect, how clients # are authenticated, which PostgreSQL user names they can use, which # databases they can access. Records take one of these forms: # # local DATABASE USER METHOD [OPTIONS] # host DATABASE USER ADDRESS METHOD [OPTIONS] # hostssl DATABASE USER ADDRESS METHOD [OPTIONS] # hostnossl DATABASE USER ADDRESS METHOD [OPTIONS] # # (The uppercase items must be replaced by actual values.) # # The first field is the connection type: "local" is a Unix-domain # socket, "host" is either a plain or SSL-encrypted TCP/IP socket, # "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a # plain TCP/IP socket. # # DATABASE can be "all", "sameuser", "samerole", "replication", a # database name, or a comma-separated list thereof. The "all" # keyword does not match "replication". Access to replication # must be enabled in a separate record (see example below). # # USER can be "all", a user name, a group name prefixed with "+", or a # comma-separated list thereof. In both the DATABASE and USER fields # you can also write a file name prefixed with "@" to include names # from a separate file. # # ADDRESS specifies the set of hosts the record matches. It can be a # host name, or it is made up of an IP address and a CIDR mask that is # an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that # specifies the number of significant bits in the mask. A host name # that starts with a dot (.) matches a suffix of the actual host name. # Alternatively, you can write an IP address and netmask in separate # columns to specify the set of hosts. Instead of a CIDR-address, you # can write "samehost" to match any of the server's own IP addresses, # or "samenet" to match any address in any subnet that the server is # directly connected to. # # METHOD can be "trust", "reject", "md5", "password", "gss", "sspi", # "ident", "peer", "pam", "ldap", "radius" or "cert". Note that # "password" sends passwords in clear text; "md5" is preferred since # it sends encrypted passwords. # # OPTIONS are a set of options for the authentication in the format # NAME=VALUE. The available options depend on the different # authentication methods -- refer to the "Client Authentication" # section in the documentation for a list of which options are # available for which authentication methods. # # Database and user names containing spaces, commas, quotes and other # special characters must be quoted. Quoting one of the keywords # "all", "sameuser", "samerole" or "replication" makes the name lose # its special character, and just match a database or username with # that name. # # This file is read on server startup and when the postmaster receives # a SIGHUP signal. If you edit the file on a running system, you have # to SIGHUP the postmaster for the changes to take effect. You can # use "pg_ctl reload" to do that. # Put your actual configuration here # ---------------------------------- # # If you want to allow non-local connections, you need to add more # "host" records. In that case you will also need to make PostgreSQL # listen on a non-local interface via the listen_addresses # configuration parameter, or via the -i or -h command line switches. # DO NOT DISABLE! # If you change this first entry you will need to make sure that the # database superuser can access the database using some other method. # Noninteractive access to all databases is required during automatic # maintenance (custom daily cronjobs, replication, and similar tasks). # # Database administrative login by Unix domain socket local all postgres peer # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32<http://127.0.0.1/32> md5 # IPv6 local connections: host all all ::1/128 md5 # Allow replication connections from localhost, by a user with the # replication privilege. #local replication postgres peer #host replication postgres 127.0.0.1/32<http://127.0.0.1/32> md5 #host replication postgres ::1/128 md5 root@debian:/etc/postgresql/9.6/main#<mailto:root@debian:/etc/postgresql/9.6/main#> segue abaixo o status do postgresql root@debian:/home/applein# systemctl status postgresql ● postgresql.service - PostgreSQL RDBMS Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2019-04-27 10:42:25 -03; 1h 11min ago Process: 2781 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 2781 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/postgresql.service abr 27 10:42:25 debian systemd[1]: Starting PostgreSQL RDBMS... abr 27 10:42:25 debian systemd[1]: Started PostgreSQL RDBMS. root@debian:/home/applein#