Hi folks! =)
This problem has plagued me for a few months already and I can't seem to find any similar cases anywhere.
An attempt to install any update (core or modules) via Backdrop's own web interface results in error:
- Error installing / updating - File transfer failed, reason //var/www/example.com/modules/[module name] is outside of the /var/www/example.com
Here's a screenshot:

This error is present on every Backdrop instance I'm managing, regardless of environment. IIRC this error started showing when core updates via web UI were incorporated into Backdrop (v. 1.12.0).
I've tried:
- Fixing file permissions -> no effect
- Updating the core manually (to 1.12.6) and then updating module(s) via web UI -> no results
- Using different PHP versions (7.1 - 7.3) -> makes no difference
I've also tried installing fresh Backdrop 1.11.4 (last version before enabling core updates), manually installing old version of imagesloaded module, and then trying to update that. This leads to a HTTP 403 error:
Failed to download imagesloaded from https://github.com/backdrop-contrib/imagesloaded/releases/download/1.x-1.0.1/imagesloaded.zip
Core versions 1.12.0 and above download modules correctly but fail to install them.
The (test) server is running Debian 9.8, Apache 2.4.25, MariaDB 10.1.37 & PHP FPM. Apache user & group owns all files, PHP FPM has same users.
Does anybody have any idea what to try next? I'm out of ideas.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists