I apologize for posting since I tried it for the first time and may be doing some silly mistake somewhere.
I’ve tried This link and this link to enable SSL on my nodejs application on an AWS Lightsail MEAN instance. One thing I’m doing is forwarding the traffic from port 80 to my nodejs app port, so that I only use the domain_name.com in the browser and not the :port.
I’m also using passportjs to implement authentication in the site and it is listening and working well on http. I even disabled the authentication part to make sure the redirect (to login) upon site access wasn’t causing the problem (but nope! didn’t help)
Every time I try to generate the certificates (./letsencrypt-auto certonly --standalone (with webroot option too as suggested in the posts)), letsencrypt gets stuck at getting /.well-known/, throws error and tells me to make sure I entered the domain correctly. I even manually created /.well-known/acme-challenge folders and created test file as according to several different forum posts and tested it via curl which worked. Then I used this tutorial too to see if setting through nginx and forwarding traffic to my application might work but letsencrypt always throws the above error.
Any help regarding this please?
The output from letsencrypt command always returns this (even though I check that the .well-known/acme-challenge exists in my views directory (where the routes are redirected)
and my hosts file also has the AAAA record to IPv6. Something silly is being done (by me) somewhere which I cannot identify anymore (beyond my hardest tries/experience that I’ve applied already). Any help is much appreciated.