Question

Refreshing DNS on a LEMP Droplet

Posted March 19, 2021 109 views
NginxWordPressNetworkingDNSLEMPDigitalOcean Droplets

Hi DO Community,

I’m in the process of moving a client’s website from an old hosting to the DigitalOcean.

Setup: LEMP on Ubuntu 20.04 (+ Wordpress, phpMyAdmin)

  1. I installed and configured SSL certificate (generated with the certbot, –certonly option) on NGINX.

  2. DNS is configured thru DigitalOcean’s Networking panel.

  3. Domain is registered by DirectNic and DNS is set to DigitalOcean’s thru their dashboard.

Issue:

When I run curl -v https://mydomain.io within the droplet I get

*   Trying 74.117.219.199:443...
* TCP_NODELAY set
* connect to 74.117.219.199 port 443 failed: Connection refused
*   Trying 74.117.219.198:443...
* TCP_NODELAY set
* connect to 74.117.219.198 port 443 failed: Connection refused
* Failed to connect to womaneze.io port 443: Connection refused
* Closing connection 0
curl: (7) Failed to connect to mydomain.io port 443: Connection refused

The IP address is not correct. It points to the old DNS handled by DirectNic.

I can confirm that my browser (after clearing the DNS on my laptop) hits a new IP using the same command mentioned above and loads the website with a valid SSL certificate.

Thanks to the Wordpress’ Site Health Status page I discovered a several Critical Issues which are related to this particular problem and would really appreciate any help/idea on how to fix this DNS issue (within the droplet).

P.S. Just for the reference… Issues reported by Wordpress:

  1. The REST API encountered an error (cURL error 7: Failed to connect to womaneze.io port 443: Connection refused (httprequestfailed))

  2. There are problems with the HTTPS connection of your website

  3. Your site could not complete a loopback request (cURL error 7: Failed to connect to womaneze.io port 443: Connection refused (httprequestfailed))

Best Regards,
Luka

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

For anyone reading this question… DNS Propagation was the issue. I just waited for a few extra hours and everything seems to be fine now.