This is not a question for /r/selfhosted. This is a configuration issue — that I am inclined to ascribe to installing too much unnecessary software — and would suggest directing to a more generalist tech support forum.
Self-Hosted Main
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
Do not delete the instance, being that it’s the free tier, you could be waiting weeks or months for another one to be made available for you. If you do end up needing to reinstall the OS, do it “in-place” on your current instance.
There are a handful of ways you could accomplish this, this one being my favorite and the one I always go to.
Ohh. You’re on that free server. I thought you had meant the big boy - 24gb memory, 4core ARM cpu free server. Yea I’ve never had a problem getting the little one deployed, probably could ignore my suggestion in this case.
Just as fyi however, tutorial may have Debian in the title, but it’s on using NetBoot.xyz which can be used to install any one of dozens of distro that they maintain and offer for net installation.
Take a look at RAM and CPU usage. Those VMs are extremely useful but have limits: swapspace is almost mandatory, lightweight custom images like debian recommendable, and CPU load should be kept low.
On the last point consider that you have just 1/8 of oCPU guaranteed, indeed the VM has two CPUs but these are for short time bursts. If CPU time is abused the hypervisor will severely throttle the instance possibly locking it (keyword: steal time).
With proper configuration there shouldn't be any problems with running reverse proxies. I have caddy running on arch and SWAG running on debian on those VMs alongside with many other containers without issues.
I had the same issue, create a swap file and use it
2G should be enough