WordPress: Pamulihan Bencana

WordPress rusak

Bencana HindenburgIng pungkasan sawetara dina I've been working furiously on getting my good friend Pat Coyle's blog back up. (My vacation continues to get more interesting – today it's snowing slightly… in April! Whatever happened to Global Warming?)

Aku pengin nuduhake apa sing kedadeyan banjur mbahas babagan pencegahan sing aku lakoni uga kepiye cara didandani.

Mangkene kedadeyan:

  1. A DNS server tindak ing fritz. A DNS server nerjemahake lalu lintas mlebu menyang jeneng domain lan pangalihan menyang server sing cocog. Kanthi kedadeyan kasebut, bener-bener ngilangi 2 cara komunikasi - jeneng domain menyang situs kasebut lan situs kasebut menyang database (basis data saiki ana ing lingkungan sing dituduhake).
  2. I complicated things by quickly moving his blog over to another server, not realizing that there was a DNS issue. This adds another level of complexity. Passwords in WordPress (and most other database applications) are uniquely encrypted by the server that they are on. If you move the site to another server, you've just disabled your ability to decrypt that password. Thankfully, WordPress (another great feature) has a password recovery system where you can reset your password via a link in an email.

Here's the immediate action that I took:

  1. Before this ever occurred, I have to say that I'm with a fantastic web hosting company who does comprehensive backups. I've never had an issue that they weren't able to correct through backups. I've heard nightmares from other folks on their blogs and sites being totally lost. I can't imagine what it's like to go through that. (Lengganan feed RSS sandi lan sampeyan bisa njaluk kupon kanggo liburan gratis karo hostku).
  2. Aku bisa mlebu menyang Web Server kanthi FTP lan njupuk kaloro situs kasebut lan database Fitur liyane saka paket hosting yaiku aku bisa ngakses kabeh VDS ngluwihi situs web asline dhewe. MySQL nyimpen database ing direktori file (/ var / lib / MySQL /). Aku bisa ndownload database kanthi nyalin direktori lokal. Dhiskusi babagan cadangan sing apik! Ora ana impor, ekspor, ukuran file maksimal kanggo ditangani ... mung FTP.

Saiki aku duwe situs lan basis data lokal, aku lega banget. Yen aku mung mandheg ing kene lan sabar, masalah DNS mesthi bisa rampung lan Pat bakal luwih cepet maneh. Aku verifikasi manawa Jeneng Domain isih nuduhake Server Jeneng sing cocog kanggo host sing digunakake Whois.net. Yen sampeyan mriksa domain sampeyan, server jeneng ana ing sangisore laporan.

Iki nggawe aku yakin manawa situs kasebut bisa uga disusupi. Server jeneng bener nanging kaca sing bakal teka kalebu sawetara kaca sing elek kaya spam. Aku nggunakke Tambahan Header Langsung to Firefox to ensure I actually wasn't being redirected – the typical hack that many people see. The site wasn't being redirected. I could have done some additional troubleshooting; however, I entered a support ticket with my host so their experts could begin investigating.

Mulihake situs sampeyan menyang akun utawa host liyane:

Aku durung nganyari Pat menyang versi paling anyar saka WordPress 2.1, PHP, lan MySQL, mula aku mutusake ora ana wektu sing luwih apik tinimbang saiki! Aku mbusak akun lawas lan nggawe akun anyar. Aku ngetik maneh informasi alias email lan ngemot basis data, WordPress 2.1 and Pat's content:

  • direktori upload-wp konten - ing kene dununge kabeh gambar sing diunggah.
  • direktori plugin wp-content - kabeh plugin sampeyan (aja nganti pungkasan amarga sampeyan duwe masalah versi.
  • direktori tema konten wp - tema sampeyan.

I hope in a future release of WordPress that these 3 directories are root directories rather than sub-directories. It would make upgrading much easier! By this time, my host had found the DNS issue and properly redirected the site. Whew! Now Pat's page was coming back up with a WordPress Upgrade message. I clicked through to upgrade the database and he was back up… almost.

Remember the encryption issue I spoke about? Yea, Pat couldn't login because of it. His password no longer decrypted the value in the database properly so I had one more correction to make. I physically logged into the database and changed Pat's reply email address in the user table to my email address. I then utilized the “Lost my Password” feature to email myself a link to reset the password. After resetting the password, I logged in and changed Pat's email address back.

And now Pat is back up! Hindsight is 20/20… had I simply waited on my host, the issue would have been corrected. I really complicated the issue. However, Pat's now upgraded and running the best versions of everything. I'm sorry he was down so long, though. It doesn't take long to bounce back from downtime, but it is a nasty inconvenience! Sorry, Pat!

Piwulang sinau:

  1. Make sure you're with a host that has great backups.
  2. Gawe serep situs lan basis data lan simpen ing lokasi sing aman.
  3. If you're with a good host, rely on them to find and correct the issue.
  4. Yen sampeyan kudu, pindhah menyang host utawa akun anyar lan ngerti cara mulihake situs, basis data, lan pulihake sandhi sampeyan.

Sawetara info tambahan

Saiki panjaluk sambungan internet cepet wis tambah akeh. Mesthi, ing jagad internet sing obah iki, telpon satelit wis kabukten regane. Nalika nerangake internet nirkabel, masarakat isih isih ora bisa takon internet nirkabel kepiye akeh regane kanggo wong-wong mau. Utamane kanggo webmaster pentinge DSL nirkabel wis ora dadi pitakonan maneh. Umume webmaster iki luwih seneng studio desain web kanggo ngrancang banjur butuh sambungan kecepatan tinggi iki kanggo ngunggah. Minangka langkah sabanjure, sambungan cepet iki uga dibutuhake ing proses marketing mesin telusuran. Wong sing duwe Sertifikasi Microsoft bisa gampang ngatasi kabeh masalah ing jaringan sambungan kasebut.

Apa sampeyan mikir?

Situs iki nggunakake Akismet kanggo ngurangi spam. Sinau babagan proses data sampeyan.