Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Accepted Answer
Hi @krestensb
I can see that your domain is using the DigitalOcean name servers, so far so good, but it doesn’t seem like you’ve created A record pointing to your droplet’s IP address.
Go to https://cloud.digitalocean.com/networking/domains and add your domain, and create an A record for @ pointing to your droplet’s IP and then create a CNAME record for www pointing to skovstedconsulting.dk
Your Apache configuration looks correct, so let’s ignore that until the DNS is done.
For a more detailed DNS tutorial with a few pictures: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-host-name-with-digitalocean
I do have the same problem with our droplet (Ubuntu 16.04 LAMP), and the solutions above didn’t work…
I’ve created the configs following the example above in /etc/apache2/sites-available/*.conf and did a2ensite in both of them, but still with no luck.
The DNS records are correctly laid out, but the browser still returns “Can’t reach this page”…
What could I be doing wrong?