Question 1

Why do the XBackBone theme dropdown, token update button, and file delete/hide controls stop working behind Cloudflare?

Accepted Answer

This happens when XBackBone is installed with an `http://` base URL while Cloudflare serves the site over HTTPS and redirects HTTP to HTTPS. The browser blocks or sends web-interface requests to the wrong scheme, so dropdowns and action buttons appear unresponsive.

Fix it by updating the base URL in XBackBone's configuration:

1. Open `config/config.php` (or the generated `config.php` path used by your installation).
2. Change `base_url` from HTTP to HTTPS, for example:

```php
'base_url' => 'https://your-domain.example',
```

3. Save the file.
4. In Cloudflare, ensure the SSL/TLS and redirect settings serve the same HTTPS domain.
5. Hard-refresh the browser (Ctrl+F5) or clear the browser cache.

After this change, the theme selector, user token update button, and gallery/table delete/hide actions should work normally. As temporary workarounds, the theme can be set from the CLI with `php ./bin/theme Lumen`, and a new user can be created to work around token generation, but these do not fix the underlying URL mismatch.

Question 2

Why do file uploads larger than 100MB fail when my site is behind Cloudflare?

Accepted Answer

Free Cloudflare plans limit uploads to 100MB per request. To bypass this, disable the Cloudflare proxy (set the DNS record from orange cloud to grey cloud) for your subdomain in Cloudflare DNS settings. This will route traffic directly to your server, removing the size restriction. No changes needed in XBackBone.

Question 3

How to fix XBackBone 3.8.0 upload stuck at 100% with saveMedia ArgumentCountError?

Accepted Answer

Edit `app/Controllers/UploadController.php`, line 62, and pass the missing fourth `code` argument to `saveMedia()`:

```php
$response = $this->saveMedia($response, $file, $user, param($request, 'code'));
```

This is fixed by PR #625; upgrading to XBackBone 3.8.1 or newer is the permanent solution when available.

If uploads then fail with `Impossible to create the root directory` or `mkdir(): Permission denied`, grant the web server user write access to the storage directory:

```bash
sudo chown -R www-data:www-data /path/to/xbackbone/storage
sudo chmod -R u+rwX /path/to/xbackbone/storage
```

Ensure all parent directories also allow the web server to traverse them. Avoid using `chmod 777` as a permanent fix.

Question 4

How to fix XBackBone 500 Internal Server Error when changing a theme in Docker?

Accepted Answer

This was caused by a broken Docker image release and was fixed in a later image update. Update to the latest XBackBone Docker image and recreate the container. With Docker Compose: ```bash docker compose pull docker compose up -d ``` With a standalone container: ```bash docker pull linuxserver/xbackbone:latest docker stop docker rm # Re-run the container with your usual docker run command ``` Clearing the application cache alone did not reliably resolve the issue. The error appeared as `Slim\Exception\HttpInternalServerErrorException` in `SettingController.php` while running `applyTheme()`.

Question 5

How do I transfer my XBackBone installation to a new host without losing data?

Accepted Answer

Download all files from the old host and upload them to the new host. If you encounter a 500 Internal Server Error, edit the config.php file to update the paths for the SQLite database and storage directory to match the new server’s absolute paths. Then you can log in normally.

XBackBone

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects