A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean
You get paid, we donate to tech non-profits.
Find and meet other developers in your city.
Contribute to Open Source
Returns an Error.
Now test this:
It works ok
Does anyone know how it works without the www?
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
You can type !ref in this text area to quickly search our full set of tutorials, documentation &
marketplace offerings and insert the link!
I'm about to host a new WordPress blog having a majority of traffic from Australia and USA, can you guys please suggest me Which data center location will be the best to host a website having a majority of traffic from Australia and USA?
I have successfully migrated my wordpress site from hostgator to digitalocean droplet. I have configured the DNS. The homepage is pointing to the digitalocean VPS but when I click other pages, it still redirects to the hostgator pages.. How do I ensure that VPS pages are being accessed ?
I do not want to delete any wordpress files in the hostgator till I am 100% sure on VPS site is working perfectly.
After uploading a theme, I activated it and it popped up a "Server Error 500". I tried to remove the themes and plugins on the WP that I just got, as suggested by some other posts. But it's still giving me the same error and I still cannot access the site. What should I do?
There are two tutorials that I have been bouncing back and forth between. They are:
Neither of these tutorials actually work. I'm sure they work for some, but these haven't worked for me.
I've gone back and forth with support about this when finally they said:
<^>I see the problem now. Certbot only attempts connection via HTTPS when using the Apache plugin. So we are going to use the manual webroot plugin instead for first time setup. Try running this command instead: <^>
```sudo certbot certonly --webroot -w /var/www/html -d domain.org -d www.domain.org```
So, that creates the cert, but then the instructions don't work anymore.
I can't be the first person to be doing this. Any suggestions on what to do next?