unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: crodges <crodges@csphy.pw>
To: help-guix@gnu.org
Subject: nginx refusing connection on port 443
Date: Wed, 25 Aug 2021 21:25:03 -0700	[thread overview]
Message-ID: <3603365.t5iAGTFeuN@sceadufaex> (raw)

Hello everybody,

I'm setting up a guix vps and having some trouble, mainly because I'm getting 
used to the guix way. After a few tries, I finally got a let's encrypt 
certificate and nginx configured to read it. Problem is, nginx accepts fine 
connections on port 80, but when I try 443 I get

curl: (7) Failed to connect to lambdashire.com port 443 after 5249 ms: 
Connection refused

My first thought was to open port 443 on the firewall, but I don't know how to 
do that and didn't find how to in a few configuration examples I searched. Is 
this the right approach, to open the port? If it is, can you please point me 
to some documentation so I can try to figure out myself?

First time posting. Thanks.




             reply	other threads:[~2021-08-26 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  4:25 crodges [this message]
2021-08-30  1:35 ` nginx refusing connection on port 443 Julien Lepiller
2021-08-30 15:44   ` crodges

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3603365.t5iAGTFeuN@sceadufaex \
    --to=crodges@csphy.pw \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).