Report this

What is the reason for this report?

FRA1: Fresh setup Droplet with Plesk is not reachable anymore after a couple of hours

Posted on May 25, 2019

I set up 5 times in a row (over a week now) new droplets with plesk from the market place. It is really painful to get it running.

After the initial setup it’s no problem to connect via ssh via putty to the server. From there i generate a one time link to setup plesk. I can login to the plesk panel with no problems. Then i set up a webspace, assign a domain and secure it with let’s encrypt. The DNS is managed by DO name servers. I synced it via the DO dns extension in plesk. After that i installed wordpress. Now the mess beginns to start:

From the computer where i set everything up i can not connect to the wordpress website. I get an 403 permission denied error. From my laptop i managed to see the website.

But the main problem is: When i come back 3-4h later to try it again (i thought of dns server update problems?) the whole server is not reachable anymore! I did nothing inbetween! Its not reachable via putty, not via web browser. Not after an reboot. On no computer. This now happened 5 times in a row! The only way i can login is with the web console on DO website.

This drives me crazy! I’m not sure if i should give DO another try.

I have a droplet on FRA1 since 3 years now with jira/bitbucket/confluence running without problems. That’s why i planned to move the website also to DO. But i see no chance anymore to get this plesk predefined setup to run properly. Any advice?



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.

Hello there,

I would like to update this question even if it’s been a while since it was originally posted.

When a droplet becomes unresponsive it is recommended to examine what caused the initial problem. You can check the logs for memory related issues (out of memory errors) and also monitor the server’s resource usage in real time to catch any processes that may cause the issue here.

You can check this tutorial on how to monitor the cpu use on DigitalOcean droplets.

https://www.digitalocean.com/community/tutorials/how-to-monitor-cpu-use-on-digitalocean-droplets

Regards

The developer cloud

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

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.