Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gr2tl-0004Ro-Rg for pgsql-general@arkaria.postgresql.org; Tue, 05 Feb 2019 15:44:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gr2tk-0005Ml-Ei for pgsql-general@arkaria.postgresql.org; Tue, 05 Feb 2019 15:44:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gr2tk-0005GD-2v for pgsql-general@lists.postgresql.org; Tue, 05 Feb 2019 15:44:32 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gr2th-0007ip-KL for pgsql-general@lists.postgresql.org; Tue, 05 Feb 2019 15:44:30 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E4D8E21F2A; Tue, 5 Feb 2019 10:44:28 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 05 Feb 2019 10:44:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=X Xr4xO3+mGGcESm2dKl0dUXmbzp97521s10OT0gTeLA=; b=dE5WGPpIhvLtyOzrW iupqhWd4vW29b5UyYHBXTgcYXaPP6vCZdjANwpC8/z5EO/a8BTR/HjgZyQs8DMMe Hr6ZzcxHWlGwrDrgz60NU5X4iM8QtxQAqlXpO1EUE/6e/gD8SW3mTt3GmY2fBoMJ C/pZl96SEV2C7MP44P/19Ty0TUzHfwEpg2KVVEaYakKip224yX+cPWKZpkTnSS7I OjKdzkkNyS/z0MPlTLFTuImZB1VtVHOrKg7hfYdkS8ezunyLAU4weTdR4iud+u5d YFq+kT2cr8GPIeGfVFmo1H469cFb6tPLxkd1U6Akj3pT8rthVPlnjvH+pMLbq/NB ZgdmQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=XXr4xO3+mGGcESm2dKl0dUXmbzp97521s10OT0gTe LA=; b=Qcs0TVtF9htCwdlOIWN1Gyi3oDjZppt4ulL/w8UzyX2q+PPmOdQguR/BB ik9rU08eVWrTdOMm/QoZYkboUKuVUsYRjOC4j7qDVQMqBtDbIv/1ABTJVjEJ5rle EPtGW3BJNbGwexi4f7gZ2BVloPyOYUq3jqwVF4/FqF/zNXLuVnmAGUdvJIjIQwjU 88RY0qebWb+OWZFDg22KPKu6fDxVR6xS/GHjvAJQ15P2fcHzgprOtv+bZ4OH17zU URl1MqQzw1DRXXyAZ8a14gAdDWAm0oYQYRA757jGKU+aJldc/9E33A95UTTctdYc A6lj8tkJknTW1Q7DoNeemhyAkeghw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrkeeigdejjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffg ggjggtgfesthejredttdefjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegr ughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucffohhmrghinhepkh grsggvlhdquggvuhhtshgthhhlrghnugdruggvnecukfhppeejuddrvdduvddrudehtddr vddtvdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrg hklhgrvhgvrhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from [192.168.1.4] (unknown [71.212.150.202]) by mail.messagingengine.com (Postfix) with ESMTPA id C7EF710310; Tue, 5 Feb 2019 10:44:27 -0500 (EST) Subject: Re: Connection issue To: Maximilian Tyrtania Cc: pgsql-general@lists.postgresql.org References: <4558AEAB-975E-495D-9001-409CD5A9E84E@gmail.com> <715197e9-84a1-d975-c29b-a3f054478c02@aklaver.com> From: Adrian Klaver Message-ID: Date: Tue, 5 Feb 2019 07:44:27 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/5/19 7:18 AM, Maximilian Tyrtania wrote: > Hi, > >> On 5. Feb 2019, at 15:57, Adrian Klaver wrote: >> >> On 2/5/19 1:48 AM, Maximilian Tyrtania wrote: >>> For some reason I can't connect to my PG 10.6.1 Server (running on Ubuntu) from my Windows installation (run via Parallels on my Mac), no matter what app I use (tried psql, PGAdmin and my own app). >> >> Has it ever connected? > > Yes, it connected without issues last week. > >> Have you recently updated any of the involved software? > > Well, sure, but after I saw I couldn't connect I downloaded the current version of PGAdmin and psql and couldn't connect with them either. > >> More below. >> >>> When trying to connect from PGAdmin 4 the server logs say: >>> 2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] LOG: 00000: Verbindung empfangen: Host=ip5b4054ce.dynamic.kabel-deutschland.de Port=50262 >>> 2019-02-05 10:34:30.558 CET [31051] [unbekannt]@[unbekannt] ORT: BackendInitialize, postmaster.c:4249 >>> 2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] LOG: 08006: konnte Daten vom Client nicht empfangen: Connection reset by peer >>> 2019-02-05 10:34:30.648 CET [31051] [unbekannt]@[unbekannt] ORT: pq_recvbuf, pqcomm.c:978 >>> ("konnte Daten vom Client nicht empfangen" means "couldn't receive data from client") >>> PGAdmin says the usual " Unable to connect to server:..." >>> No issue connecting from the Mac. >>> I see in the logfile that other windows users did connect successfully from their windows boxes so I am ready to believe that maybe my Parallels somehow disconnects the connection quickly or something. >>> Another strange thing is that if I try to connect from my Xojo app (which uses libpq internally) it says:SSL error: unknown protocol. I had no issue connecting last week from that installation so I am at my wits end... >> >> Where is the Xojo app running? >> >> Is the pg_hba.conf on the server set up to allow connections from the client machines? > > Yes. Also the errormessage wouldn't be "Connection reset by peer" if it was a pga_hba.conf issue, would it? And anyway, I can connect just fine from my Mac with the same credentials. I wonder if this is maybe some Parallels issue. Well if you could connect from Parallels last week, you upgraded it and now you cannot connect then I would suspect it. This assumes that the Xojo app is also running in the Parallels instance. Given the SSL error you might see if they changed anything in that area. > > Thanks, > Max > -- Adrian Klaver adrian.klaver@aklaver.com