Plugin Contributor
bcrodua
(@bcrodua)
Hi,
Please can you check if the WordPress Address (URL) and Site Address (URL) on your website is set to https?
Regards,
Bryle
Hello bryle: In 1st. place, thanks x answer
Regarding your question, in fact, both parameters are in https, as you can see following this link;
https://www.dropbox.com/s/rk3s0dtfshxyhb7/Captura%20de%20pantalla%202019-07-17%2007.36.48.png?dl=0
On the other hand, this is the text of the message in question (in Spanish, heh!);
https://www.dropbox.com/s/ujvxl34xldv75is/Captura%20de%20pantalla%202019-07-17%2007.43.35.png?dl=0
And before you ask me, I attach, also, a copy of the record (log);
https://www.dropbox.com/s/22acgxpm0saf478/log.3da779bbad11.txt?dl=0
Frankly, it’s a pity because, strictly speaking, it’s the only “defect” I see in v / plugin. But bueh!
I have also read some answers that other users received with the same problem.
Answers of the type … “it’s just cosmetic” … and / or that … “ignore that message” …
But, frankly, why risk and / or “scare” us unnecessarily, right?
If there is a solution, would not it be good to implement it in future updates?
I await (anxious) v / comments.
Thank you.
Greetings.
PD1: Actually, I’ve found out about other plugins but, honestly, yours stands out above all in questions such as …
1) It is very easy to configure.
2) It connects to Google Drive “in a twist” and, without big “settings”.
3) It allows you to restore EVERYTHING, also … “in a touch” …
PD2: However, could you solve the backup with wp-cron deactivated?
Sure you know the pros and cons of keeping said wordpress native cron and, frankly, to “satisfy” the “needs” of a plugin is a “mischief” have to leave said cron active so that Updraftplus can perform ONE ONLY task (do a daily backup).
For my part, I solved it by creating a cron task that is activated per minute. That is, more than enough time for Updraftplus to complete its task.
I mention them because, this inconvenient, other backup plugin already have it resolved.
By last…
PD3: Is there any possibility to establish a communication in Spanish? (I’m using a translator so, of English, nothing 🙂
Thanks, again.
Another yes, I say.
Hello again:)
In relation to this topic, I have just “discovered” the following:
When the plugin is set to “Daily” (Programmed Copy) and, I make a manual copy (after the “established” time), when wanting to restore the copy generated in said “scenario”, I see the same error as the one described above .
That is, said copy, too, appears as done in an http site when, as I said, my site is https.
This I just observed when, doing tests, to see if I could solve the problem on my own and, reading other answers to users of this plugin that, manifested the same problem, I changed the settings from “Daily” to “Manual” and, I proceeded to make a backup which, when wanting to restore, threw the “famous” error of … “was done when your site was on http” …
In summary and, in my humble opinion, the problem is in the programming process.
That is, when the plugin is “programmed” (either “Daily” or “Manual”), the site’s backup fails.
I hope this helps solve the problem as soon as possible.
Thank you.
Greetings.
What is it that you mean by “saved in http” ? A backup of the files + database in your WP installation is a backup; there is no concept of “an http backup” or “an https backup”. It is just a backup. I’m guessing you are reading the log file? This is just the result of asking WP for the site address, but is entirely cosmetic – it has no effect on the backup itself.
Hi.
No. I mean what I mentioned earlier, that is to say …
… “On the other hand, this is the text of the message in question (in Spanish, hehe!)
https://www.dropbox.com/s/ujvxl34xldv75is/Captura%20de%20pantalla%202019-07-17%2007.43.35.png?dl=0
That is, as you can see, it is the error message that appears on the screen, when you try to restore the backup made by the plugin, in an “automatic” way.
Ergo, if as you say … “there is no concept of” a backup http “or” https a backup “…
So that the message with the “clarification”?
Do not you realize that, as the comments in other threads, this is something that “scares” us?
By last,
Would you bet the reputation of your plugin that, as you say … “is totally cosmetic” … and / or that … “has no effect on the backup itself” …?
And what about the 2nd part of the message?
That which says …
… “Warnings:
This backup is from this site, but at the time of the backup you were using http, and now the site uses https. As your web hosting allows http (that is, non-SSL access) or redirects requests to https (which is almost always the case) there is no problem. If this is not yet configured, you should do it now, or use the migration extension so that non-https links are automatically replaced.
You can search and replace in your database (for the migration of a website to a new location / URL) with the Migrator plugin – follow this link for more information “…
Yes, as you say … “it’s purely cosmetic” … then, what’s the warning?
I await v / comments.
Thank you.
Greetings.
Dear:
Unfortunately, yours is getting worse 🙁
Now in addition to the warning that we have been “talking”, that is …
This backup is from this site, but at the time of the backup you were using http, and now the site uses https. As your web hosting allows http (that is, non-SSL access) or redirects requests to https (which is almost always the case) there is no problem. If this is not yet configured, you should do it now, or use the migration extension so that non-https links are automatically replaced.
You can search and replace in your database (for migrating a website to a new location / URL) with the Migrator plug-in – follow this link for more information
All of which, you can see in the screenshot that you will see by clicking on the following link …
https://www.dropbox.com/s/tb0o00visn2p7pv/Captura%20de%20pantalla%202019-07-24%2003.33.10.png?dl=0
As I said, now also, this other warning appears to me …
The backup of this database has the following WordPress tables excluded:
Which you can see by following this link;
https://www.dropbox.com/s/b2xzgf1w6egedgm/Captura%20de%20pantalla%202019-07-24%2003.34.16.png?dl=0
In case of doubt 1
Attached I send you link of my current configuration …
https://www.dropbox.com/s/o9ab8fao1dxh6x3/Captura%20de%20pantalla%202019-07-24%2003.37.45.png?dl=0
In case of doubt 2
I also send you a copy of the Registry (log) of the backup in question …
https://www.dropbox.com/s/3x872rdppunic5a/log.2ca02e834676.txt?dl=0
Can you answer yes, can you offer me a solution to both problems?
I await comments.
Thank you.
Greetings.
PD: Of course, I will wait a while and, I will proceed to delete this last backup. Which leaves me without daily backups and, therefore, if I cannot resolve it as soon as possible, I will have to change the plugin.
Strictly speaking, it is a real shame because, until now, you were the best backup plugin I had tried but, for some time now, this has changed for the worse.
One way or another, same, thanks.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Disclaimer: I use the commercial UpdraftPlus plugin and I am a customer of this author. I like to get that out of the way. I’m also a forum moderator on ww.wp.xz.cn which is why this came to my attention.
@atutrabajo I have archived your new topic, please do not create duplicate topics or topics about topics. Your new topic is still there but only other forum moderators can see it.
I get that you are frustrated but I want to remind you that you are not a customer here. David is not a company here either. This plugin is opensource code and you are a user of that free code. David is a volunteer here; there are no companies here only volunteers.
Free users have a totally different relationship with volunteer plugin authors. If you were a customer seeking support then I would close this topic and direct you to their site. Customers are not for here.
If this plugin is not working out for you then perhaps you want to consider using another free backup plugin? There are others to choose from on this site.
-
This reply was modified 6 years, 10 months ago by
Jan Dembowski. Reason: Silly grammar mistake
