Problems:
/home/austen/, /home/firth/, etc. AND inside /home/wholetec/public_html/. Which one is actually being served?Result:
/home/wholetec/public_html//home/IMPORTANT: Everything is backed up on GitHub. If anything goes wrong, you can restore from there. This is safe.
We need to confirm: are the sites at /home/austen/, /home/firth/, etc. actually being served, or are they old copies?
In WinSCP, check if there's an austen folder inside /home/wholetec/public_html/ also. If yes, the /home/austen/ one is probably the old copy.
Test: Make a tiny change to a file in /home/wholetec/public_html/ and see if it shows on the live site. That confirms the web root.
If austen, firth, tvreviewer, and carolekatchen are NOT already in /home/wholetec/public_html/, copy them there:
/home/austen/ → /home/wholetec/public_html/austen//home/firth/ → /home/wholetec/public_html/firth//home/tvreviewer/ → /home/wholetec/public_html/tvreviewer//home/carolekatchen/ → /home/wholetec/public_html/carolekatchen/Use WinSCP drag and drop. Verify each site loads at its URL after moving.
In /home/wholetec/public_html/, delete these WordPress files/folders:
wp-admin/wp-content/wp-includes/wp-config.phpwp-login.phpwp-xmlrpc.phplicense.txt, readme.html (WordPress default files)Keep: index.html, static/, bergeron/, links/, robots.txt, .htaccess (if it has redirects you need)
Your sites are all static HTML. WordPress is dead weight and a security risk.
Once sites are confirmed working from public_html, delete the old copies from /home/:
/home/austen/ — delete (now in public_html)/home/bnbhot/ — delete (lives in bergeron/bnbhot.com/)/home/firth/ — delete (now in public_html)/home/tvreviewer/ — delete (now in public_html)/home/carolekatchen/ — delete (now in public_html)/home/wholetech/ — delete (empty, confusing duplicate)Don't delete yet:
/home/wholetec/ — this is the actual web root, KEEP/home/clamav/ — system antivirus, KEEP/home/cybersubdivision/ — check what's in it first/home/vitfs/ — check what's in it firstBefore deleting, check what's inside:
/home/cybersubdivision/ — is this an old project? If you don't recognize it, rename to cybersubdivision.OLD and see if anything breaks./home/vitfs/ — might be a system folder (virtual filesystem). Don't delete without checking.That huge .tar.gz file in /home/ is probably an old server backup. It's wasting disk space and everything is on GitHub now anyway.
Before deleting: Check the filename and date. If it's older than a month, it's safe to delete. Your real backups are on GitHub.
We tried to set up SSH key auth yesterday and it failed. The key is in /root/.ssh/authorized_keys but the server rejects it. Possible fixes:
/etc/ssh/sshd_config — make sure PermitRootLogin is set to yes or without-passwordPubkeyAuthentication yes is in sshd_configsystemctl restart sshdWith SSH working, future server management becomes much faster — I can run commands directly instead of you navigating WinSCP.
You're paying ~$86/mo for Liquid Web. All your sites are static HTML — no PHP, no database, no WordPress needed. Options:
Potential savings: $86/mo → $0-5/mo = $81/mo saved ($972/yr)
Not urgent — do this after everything else is stable.
Everything is on GitHub. All 13 sites were pushed on March 30, 2026. If you delete something by mistake on the server, you can restore it in minutes from GitHub. This cleanup is safe.
Before deleting anything on the server, always verify the site still loads from its new location first.