Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lxrO0-00075r-N6 for pgsql-novice@arkaria.postgresql.org; Mon, 28 Jun 2021 13:33:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lxrNz-0004Nc-9G for pgsql-novice@arkaria.postgresql.org; Mon, 28 Jun 2021 13:33:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lxrNy-0004NT-TM for pgsql-novice@lists.postgresql.org; Mon, 28 Jun 2021 13:33:15 +0000 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lxrNs-0004qu-02 for pgsql-novice@postgresql.org; Mon, 28 Jun 2021 13:33:14 +0000 Received: by mail-wr1-x436.google.com with SMTP id a13so21285993wrf.10 for ; Mon, 28 Jun 2021 06:33:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=8MT9+0KSSsJHvu6Tik0ynnUkxdppCo4PXpvUc+fOKZc=; b=RUZluiNW1/eSYzhJm/QBfm5pG9sG2g0MF382Mn/KoJ1ZWdENWhutvrad64hXSXebQ6 sTPP8r5Uls6v+89z1dlHIWSb5qWJ+BzGjTDBjN6XzWL7zzKFHLfux1+HwPYyS6zWI8I5 of245UuR73YhuWB18jO6ccGKAqE5q2CvVSEIiL3NooFWxV8nLLv74FTSgsmCIXBg2AJa xwhkz24wWDeHXFd5KjuCFSgsEhhe08mVE9bl9ECTEOSn5iUM9Z+eI7jSxpgS9d/maY0r /goHNPhKHBxU6gu1B/LTvB062LAwU+Inv3zEWeP6IeWvYdShRriPbVKg+wiMeFhbkU/b okXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=8MT9+0KSSsJHvu6Tik0ynnUkxdppCo4PXpvUc+fOKZc=; b=k4PiV27mEo4ovM0A4LB96gUTpuv96Kxf9fapOOUs8Z2MG5ekjtcXkmxZND/033W+35 esCyRQjPn39vAcklaQuLdQ5UWY9l6JADYRVP/3AOaGC/wVjSeZIHHgc+/stskyTJW1Yt QFPjMrqEOyGzdIiuvQL5IvpNG3N4rA563jME9lNwjE2ek5by3T+pZ9wwqgcmukwfGtRw xed8aBaMhTiP1lI/kMvlnJTBjIhEPPRSl1yjFpt/wMW/jCIiivDZXO4ynry34LfT+fCP 5dgP+pfuvSz++Njn/5RePM+oOyPHBcpuiVvdHMhRvy3adwloB/HqqeYAnTkPETlZWSZi 8Y5w== X-Gm-Message-State: AOAM5325b5uf1CSnB2CzkJNEXO+tBUYcbqaIPnBBUzk4VT+MmAiNebTh QSlhnZM3Sd/Rewen0g84LlLdqA== X-Google-Smtp-Source: ABdhPJykgGI4aUxK3F5E8+9bv6rGwF07sm0gDfP6qaQOqaW3dKQyV5TNZUk7+snIvGBG33MwnHESZg== X-Received: by 2002:adf:cc87:: with SMTP id p7mr28414000wrj.105.1624887185965; Mon, 28 Jun 2021 06:33:05 -0700 (PDT) Received: from localhost.localdomain (217-149-171-124.nat.highway.telekom.at. [217.149.171.124]) by smtp.gmail.com with ESMTPSA id a9sm14500433wrv.37.2021.06.28.06.33.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Jun 2021 06:33:05 -0700 (PDT) Message-ID: <9935482c0bc0ba92e9cada7ade741e090023d6db.camel@cybertec.at> Subject: Re: server.crt Missing From: Laurenz Albe To: BeeRich Lists , Submit Postgresql Novice Date: Mon, 28 Jun 2021 15:33:05 +0200 In-Reply-To: <0A2DE29C-2A64-48AF-8AC2-045408A4DD49@gmail.com> References: <0A2DE29C-2A64-48AF-8AC2-045408A4DD49@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2021-06-28 at 09:04 -0400, BeeRich Lists wrote: > I’m getting repetitive errors/warnings: > > 2021-06-28 08:57:07.127 EDT [44717] FATAL: could not load server certificate file "server.crt": No such file or directory > 2021-06-28 08:57:07.127 EDT [44717] LOG: database system is shut down > > This is my workstation, so I don’t have a certificate for this. Is there a way I can get this to not be reported? I’ve checked nginx.conf and there’s nothing in there that shows me that I can turn > this off. > > Any insight appreciated. If you want transport encryption with TLS, you have to provide a server key and certificate. If you don't need that, set "ssl = off", then PostgreSQL won't complain. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com