Hello. Thank you very much for your answer. The configuration actually works for me. After restarting my computer, I went to test again and it was already working. I assume that perhaps because they are virtual machines it was not only enough to restart the server, I think you also had to restart the computer. It's what I think, or I don't know what else could have happened, but now it's working for me. Thank you very much and greetings, Yessica Brinkmann
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre de virus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> El vie, 12 nov 2021 a las 15:37, Adrian Klaver (<adrian.kla...@aklaver.com>) escribió: > On 11/12/21 10:34 AM, Yessica Brinkmann wrote: > > Thank you very much for your answer. > > Did you find the problem? > > If not have you investigated whether whatever changed the IP also > enabled a firewall rule that blocks port(5432 I'm assuming)? > > > Regards, > > Yessica Brinkmann > > > > > > El vie, 12 nov 2021 a las 9:22, Dave Cramer > > (<davecramer@postgres.rocks>) escribió: > > > > > > > > > > On Fri, 12 Nov 2021 at 06:12, Yessica Brinkmann > > <brinkmann.yess...@gmail.com <mailto:brinkmann.yess...@gmail.com>> > > wrote: > > > > Hello. > > Thank you very much for your answer. > > Yes, I restart the server after making the changes. > > Regards, > > Yessica Brinkmann > > > > > > Check the logs for postgres to make sure there were no errors in > > your new configuration. > > > > Dave Cramer > > www.postgres.rocks > > > > > > > -- > Adrian Klaver > adrian.kla...@aklaver.com >
