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.

I’m getting “504 Gateway Timeout” error on the production site, and I know I’m pointing to the server because if I access this route https://165.227.0.69:8080/test I get the expected result.
I ran in this while looking for answers:
I ran the commands described above and got the following results:
total used free shared buff/cache available Mem: 985 190 192 0 602 642 Swap: 0 0 0
Linux 4.15.0-51-generic (ubuntu-s-1vcpu-1gb-sfo2-01) 06/11/19 x86_64 (1 CPU)
14:07:05 CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle 14:07:05 all 0.31 0.01 0.07 0.28 0.00 0.00 0.01 0.00 0.00 99.33
The first one it’s confusing since it shows that we have as free memory only 190 but then it shows 642 as available? The post said this error could be related to not having enough memory for the server, but how can I be sure about this?
I have 2 html websites and this angular firebase application (which we’re trying to configure with socket.io) running on a 1 GB Memory / 25 GB Disk / SFO2 - Ubuntu 16.04.5 x64 which has been upgraded to 18.04.
jeffs
0621335d663b4b699a60eb27e28153
accesstrax
Dwight Trumbower
admin
yimprogramming
samunyi90
1d6ce141ab5444dfb1ea2dd29cf4b1
Matt Fricker
joel9b158e40551b15093f213f
EmilJacobs