robnicholson

BTW – before we migrated, we’d switched to Updraft Plus! backups to Google Drive. Worked well but we were using a free Google account so limited to 15GB which was about four days of backup.

>I’m still using GoDaddy for my DNS.

Same here but only until that service expires and then it’s moving as well. Just don’t trust them anymore. I once had the displeasure of migrating M365 email from GoDaddy to Microsoft 365 hosted. I’ve still got the grey hairs to prove it. What a disaster. It took them FOUR days to release the domain from their tenant so it could work with M365. Four days of lost email. Each time all I got was “We’ve released it, give it two hours”.

Anyway, this is about UpdraftPlus, an excellent product. Hostinger offer free backup but it’s only weekly but better than nothing. So we still run UpdraftPlus backing up to client’s own FTP server.

• This reply was modified 3 months, 1 week ago by robnicholson.
• This reply was modified 3 months, 1 week ago by robnicholson.

Yes but you don’t really want to hear it. I migrated the three charity websites to Hostinger where UpDraftPlus! works flawlessly. GoDaddy is no longer a very good host IMO. Lots of big adverts on TV but when we reviewed the costs, Hostinger was at least half the price (free SSL was a clincher). This problem was the final straw and it coincided with annual renewal. I was very pleased with the Hostinger admin console which is easier to use than cPanel which I’ve always found rather sketchy. Not using cPanel also saves a bit on license costs.

I had one query for Hostinger and I got an answer via chat in minutes. The person I was chatting with clearly knew what they were talking about. Another black mark for GoDaddy. I fear having to contact their support.

Even in the dying throws, GoDaddy annoyed us by changing the DNS records to point to parking when the hosting package expired. Why!!!

• This reply was modified 3 months, 1 week ago by robnicholson.
• This reply was modified 3 months, 1 week ago by robnicholson.

Will do but it might be a while before I can test the restore again. This is a live server so time to experiment is limited. It’s not a mission critical system – a charity website, so I can work at weekends.

I do yes.

It’s worked flawlessly for years so either UpdraftPlus changed something or GoDaddy did. I managed to restore a backup from 20th July when backups were working with an older version of UpdraftPlus – same problem. So fingers very much pointing at GoDaddy. I’m restoring a backup to a server in my dev environment as a test.

The restore eventually stopped with a continue or dismiss prompt. I did a continue but then it reports that one of the ZIP files is missing: https://i.imgur.com/8APi76E.png

Looking in the updraft folder using FTP and that file has been corrupted: https://i.imgur.com/dzXhmL5.png. Notice how the file size is now zero bytes (!) and the time stamp has been modified, i.e. something has written to the ZIP file…

I’m going to have to give up with UpDraftPlus restore and see if I can unpack the ZIP files manually.

PS. I’m more than happy to accept this is crap GoDaddy hosting. The hosting is up for renewal in a week so I’m urgently looking at another host.

• This reply was modified 7 months, 3 weeks ago by robnicholson.
• This reply was modified 7 months, 3 weeks ago by robnicholson.

You’re not with GoDaddy by chance are you? Because our FTP backups have failed too but with a different error. Ours seems to be more firewall related. I’m just about to restore an earlier backup of the website from 20th July when backups were working to isolate UpdraftPlus or GoDaddy.

>My server has had SSL connections for a while, it’s not new. I solved it by installing a different plugin.

Do you mean you stopped using UpdraftPlus?

I updated our website an hour or so back and the problem was still there so I restored the backup. Tickets for the beer festival had to go online today so I’ve stuck with not updating the plug-in. Seems to be working okay as 20 tickets sold already.

Phew, thank goodness there’s a fix. Just come to put the beer festival tickets on sale and got this problem.

I didn’t spot this error on my pilot site as PHP error reporting was off by default. I’ve just added the following to wp_config.php which hides the error until it can be fixed:

ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, false);
define(‘WP_DEBUG_DISPLAY’, false);

I’ve turned error reporting on in my pilot site and the error now displays there. So can test if a fix works before adding to live.

Text copy of the error:

Warning: Undefined variable $grid in /usr/share/nginx/pilot.bbf/wp-content/plugins/my-calendar/my-calendar-core.php on line 519

• This reply was modified 2 years, 10 months ago by robnicholson.
• This reply was modified 2 years, 10 months ago by robnicholson.

Thanks Joe – will give it a go. Need to make a donation as MyTickets is a godsend for a small charity. Cheers, Rob.

Later… the original VM was built under VMware Workstation. I’ve just gone through exactly the same build process on a Hyper-V based VM and Photo Gallery works fine! So I’d ignore this one – must be a problem at my end.

I notice that it seems to do stuff in blocks of 5. If you watch wp-content/uploads/photo-gallery, you see file images appear, then a big pause, then another 5 etc. What exactly is it doing after the image is uploaded? Don’t think it’s generating the thumbnail as those appear almost immediately after the image appears in the root photo-gallery folder.

I’m uploading 80 photos with a total size of 103MB so not exactly massive numbers or sizes.

• This reply was modified 2 years, 10 months ago by robnicholson.
• This reply was modified 2 years, 10 months ago by robnicholson.

Okay, adding client_max_body_size 20M; to the NGINX configuration gets rid of this error but it then introduces another:

2022/05/08 16:49:18 [error] 63574#63574: *1197 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.54, server: pilot.bollingtonbeerfestival.co.uk, reque$

So will now look at that one…

Ahh, mine might be a file size configuration problem:

2022/05/08 16:33:17 [error] 11282#11282: *1149 client intended to send too large body: 5162392 bytes, client: 192.168.0.54, server: pilot.bollingtonbeerfestival.co.uk, request: “POST /wp-admin/admin-ajax.php?bw$

Later…

• This reply was modified 2 years, 10 months ago by robnicholson.