rotem925

Thanks for this update Anthonius!

Looking forward to update asap!

Rotem

Hi @kingyes, of course, I have many parameters, one of them is HTTP_X_FORWARDED_FOR. I thought the purpose of choosing HTTP_X_FORWARDED_FOR as an option in the dropdown will pick this.

I really think this should be part of a fix of the plugin. This is very common to have this with multiple load balancers. See this https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For

Thanks,

Rotem

Hi @anthoniusalfred checking back, I see another release of updraft, does it include this fix? Couldn’t find this in the ChangeLog.

Thanks,

Rotem

That’s perfect!! Thank you for this update!

Rotem

Hi there,

I see a new version without the fix you sent me. When is it planned to be officially released?

Thanks!

Rotem

Just checked!! Works perfectly ! I just tested the uploads folder though..

Thanks a lot !

Great news ! Thank you for this quick fix. I will test it right away.

Will this also handle any mounted folder? Say for example the languages folder?

Great, thank you for the response.

Waiting to hear on on this issue.

Rotem

Hi,

two containers? I only have a single container for WordPress. The permissions are set correctly on the volume. Something I’m making sure of before running the container (again, single container).

If you’re referring to the volumes, both volumes have the same permissions for the user that is running the webserver.

It is actually very easy to reproduce, with any compose stack that includes WordPress.

See this compose I’ve just created for you to test, upload any file, install the plugin, and try to restore, you will reproduce this error immediately.

Let me know if you need any assistance from me with pleasure. And thank you again for your help on this! We really want to apply this plugin to our WordPress sites.

Here is a link to the compose in pastebin:

https://pastebin.com/4wxD91su

Yes, I’m using NFS as well, actually, that’s EFS on AWS Elastic Container Service.

BUT, that happens also on my local machine, which use a normal mount using docker-compose, no NFS here, same exact error.

I mount only the uploads folder, the updraft folder is inside the container volume (different one), I do not mount it into a different folder.

• This reply was modified 1 year, 4 months ago by rotem925.

Of course, there you go: https://pastebin.com/sxAE58fD

I’ve tried to restore only the uploads folder to make the logs smaller.

It is pretty easy to produce with any mount to uploads folder

I think you are trying to rename the uploads folder which won’t be possible if that’s a mount point of course.

Thanks

• This reply was modified 1 year, 4 months ago by rotem925.

Dude,
Please add this. It solves alot of issues. This requires me to maintain your plugin on each update!