Unable to point domain name to digital ocean Wordpress droplet ip address

May 12, 2017 3.5k views
WordPress DigitalOcean DNS CMS Ubuntu 16.04
5d374e485a74d7814333082b5f75d256440fee64
By:
robneal28

Hey guys I’m having a problem pointing my digital ocean Wordpress droplet to a domain name I have. I’ve already been through this tutorial https://www.digitalocean.com/community/tutorials/how-to-set-up-a-host-name-with-digitalocean and at the moment:

test.dumontocdhelp.com ,
www.dumontocdhelp.com ,
or anything else before .dumontocdhelp.com will redirect to my
droplet’s ip address [ http://45.55.244.247 ].

However If I try dumontocdhelp.com i get redirected to https://dumontocdhelp.com/ which gives me an error page that says

This site can’t be reached
dumontocdhelp.com refused to connect.

Not sure if it has something to do with the https, any help would be great.

** Also yes I did make an A record to also connect my IP to a domain name with nothing before it for dumontocdhelp.com *

Sign In to Comment
2 Answers
jtittle1 May 12, 2017

@robneal28

If WordPress was installed using the Droplet IP, then WordPress is using the IP address pulled from the environment/URL/headers. To change the URL that WordPress uses, the easiest method would be to edit wp-config.php and add in:

define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');

Change example.com to your domain in each define(). You’d then refresh the page and that’ll set the domain that WordPress uses to your domain.

Once the domain is updated, you may need to make one more change and that’d be to Apache and the VirtualHost block that your domain uses.

Your VirtualHost blocks are located in /etc/apache2/. You’d need to change the IP being used for the host to your domain and then restart Apache using:

service apache2 restart

As long as your DNS is correct, that should fix issues with your domain not working.

Report
  • robneal28 May 16, 2017

    Thanks for the help it didn’t work and I ended up not really using my digital ocean droplet but I appreciate you answering.

    Report
  • myidealab May 13, 2018

    This did the trick for me. Except, I didn’t fully understand the VirtualHost blocks procedure. I went to the /etc/apache2/ folder, but it was unclear what file I am supposed to edit. So, I restart Apache and tested WordPress on Edge, Brave, Firefox, and Chrome. This resolved the CSS rendering issue I was having as well.

    Thank you!

    Report
RightSide January 27, 2018

I’m having the same issue.

Report
Have another answer? Share your knowledge.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Related