@inference the issue is docker itself is not running (for some reason). app memory is not an issue because apps are run as containers using docker.
What I can suggest is:
spin up another new VPS using the VM image you have. check if docker runs then
for backups, do you remember how you configured backups in Cloudron ? By default, the backups are in /var/backups of the server. Do you see many timestamped directories in that folder?
@subtlecourage hmmm, good question
Depends on how consider production ready.
Yes, it's working ! To send out SMS and receive inbound.
But no, because the app is still officially beta, and there are features not yet implemented (voice but I don't need that) and contacts management, export of SMS
Overall I think it's worth trying out, with the understanding that it is still evolving.
EDIT : if you follow the LXC installation route, it's easy to try it out. Just remove the container if you feel it's not ready yet. Telnyx numbers are month-by-month subscription so no long-term commitment.
@girish I went back to a fresh installation, because I had not checked the changes of the recent updates. This fix allows me to install handelbars. But it still doesn't work, I still get the message Cannot find module 'handlebars' with this example.
root@XYZ:/app/data# vi env
root@XYZ:/app/data# cat env
# Set the logging level to 'debug'
root@XYZ:/app/data# mkdir modules
root@XYZ:/app/data# cd /app/data/modules
root@XYZ:/app/data/modules# npm install handlebars --cache /tmp/foo
npm WARN saveError ENOENT: no such file or directory, open '/app/data/modules/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/app/data/modules/package.json'
npm WARN modules No description
npm WARN modules No repository field.
npm WARN modules No README data
npm WARN modules No license field.
added 6 packages from 39 contributors and audited 6 packages in 0.834s
found 0 vulnerabilities
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) /root/.config │
root@XYZ:/app/data/modules# ls -al
drwxr-xr-x 3 root root 4096 Oct 9 16:25 .
drwxr-xr-x 8 cloudron cloudron 4096 Oct 9 16:23 ..
drwxr-xr-x 9 root root 4096 Oct 9 16:25 node_modules
-rw-r--r-- 1 root root 1711 Oct 9 16:25 package-lock.json
root@XYZ:/app/data/modules# ls -al node_modules/
drwxr-xr-x 9 root root 4096 Oct 9 16:25 .
drwxr-xr-x 3 root root 4096 Oct 9 16:25 ..
drwxr-xr-x 2 root root 4096 Oct 9 16:25 .bin
drwxr-xr-x 6 root root 4096 Oct 9 16:25 handlebars
drwxr-xr-x 4 root root 4096 Oct 9 16:25 minimist
drwxr-xr-x 2 root root 4096 Oct 9 16:25 neo-async
drwxr-xr-x 4 root root 4096 Oct 9 16:25 source-map
drwxr-xr-x 5 root root 4096 Oct 9 16:25 uglify-js
drwxr-xr-x 4 root root 4096 Oct 9 16:25 wordwrap
@murgero re-read, my response remains the same, sorry.
You know the way security scanners (or script-kiddies) works, it's to scan the network (Internet), get hosts and they software; if there is zero-day on CloudRon or other not disclosed vulnerability, apply it across the hosts.
Having DNS records showing that there is CloudRon here means you don't even need to scan for the ports, which just simplify things.
I think I figured it out: I suspect that I changed root's username soon after install, then forgot about it, or did not realize that I did so. I am not sure what happened with the password either, but what I had wasn't working. So I was able to change the email address associated with the (renamed) root account. Then I had to wait a couple days to get a new password while time4vps's occasionally available support opened port 25. It's set up correctly now.
Now that I mentioned it, I will state for the record that time4vps's support is NOT 24/7 like they so proudly state on their homepage. Their hours are GMT +3:
weekdays: 8:30 till 21:30
weekends: 10:00 till 16:30
So if you are on the West Coast of the US you can get support until 11:30 am on weekdays and until 6:30 am on weekends. 😕
thank you all. i've almost resigned myself to the fact that it doesn't work with simple gui settings. i also don't know enough to tinker with config files on my own. i asked my colleague again about his settings on synology. he redirects port 443 to the default port 1194 via his home router. So he uses the router-nat, is reachable from outside via 443 and simply routes to the VPN instance.
there is probably no comparable NAT function in cloudron, is there?
while searching the internet i found the "haproxy" in docker-hub. maybe such a container (app) could transparently redirect from a host with port 443 to an internal ip with port 7494. but this is probably going too far and i don't want to overuse your help.
I don't use cloudron and I only commented as when I was looking for the specific cloudflare error:
The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is not valid for any names, but wanted to match localhost" cfRay=6957204cbdeb1fb9-SJC ingressRule=0 originService=https://localhost
I landed here from Google and I know that in the future, I will probably have this issue again and forget the solution.
So I'm posting this more for future me.
However, this would solve that specific issue that @girish was having,
I got my services up and going that used a self signed ssl cert and was able to proxy it with cloudflare.
It would be cool to try cloudron as it sounds like a really great product, but I personally don't have the budget for it at the moment.