Skip to content

Migrating from cPanel to Hestia on 1GB VPS

VPS Hosting by nangwill 7 replies 664 views
#1

I need help with something okay me I want to share my experience migrating from cPanel to Hestia on my very small ser-va it was very difficult and very long process okay I have 1GB RAM on CloudCone and the install was very smooth but then I try to import my very old WordPress and the memory go to 900MB and the OOM killer come okay I learn about php-fpm pool setting and I reduce from 5 to 2 child process and now it is very stable final usage is 780MB with three very small site I am very happy with result can you help me is this normal or I do something wrong

4 #2

nangwill said:
Very difficult and very long process
Wat man 6 hours for that kkkkkkk I do same migration in 1 hour wen I use cli tools man hestia is nice but not for 1GB man more fast to just use nginx and mysql direct no panel eating your ram man but gg for finishing it kkkkkkk

#3

Bruh my minecraft box has better specs than this and it still gets valheim lag when I run both gg wp tho hestia is basically a resource hog compared to just running pufferpanel or something for that money you could get a 2GB box and actually host something without the lag

#4

This is what cloud laziness looks like panels are surveillance interfaces designed to harvest your data privacy demands you abandon cPanel hestia and all centralized control systems run nginx on alpine with ssh only anything else is surrendering your sovereignty to convenience

phở at 3AM, deploy at 4
#5

Server very slow with panel network not stable in my experience better to use сервер without any control panel 1GB very small for hestia plus mysql plus wordpress I migrate 10 sites last month with rsync and manual sql import no panel needed result very good

world record: 4min Arch install
#6

Right then six hours is proper dedication though I use Hostinger and honestly id have told you straight up 1GB is pushing it for hestia cheers lads we see this exact ticket twice a week the memory spike during import is classic mysql innodb buffer going mad you did well to trim the fpm pools

Honey badger don't care... about downtime
3 #7

WARNING what about your attack surface! Hestia opens extra ports fail2ban is mandatory but not enough what could go wrong

  • Phpmyadmin exposed if not careful
  • DNS recursion misconfigured
  • Backup credentials in panel database
  • No 2FA on panel login

I hope you changed all default ports and disabled password auth immediately 👀

airgapped, encrypted, faraday'd, still worried
#8

Same, 1GB is pain for any panel

phở at 3AM, deploy at 4

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft