[BUG] 1.6.11 clean not docker installation failure, another error

[wgh-control]

What happened?

Now i cannot download files with curl during installation

How to reproduce?

Clean OS and installer script, i also changed OS to Rocky Linux 10, i was thought maybe it network connectivity issue, i started VPN on my VM - same issue.

Configuration file(s) (yaml or .env)

Relevant log output

[INFO] Skipping host_config phase (already completed in the interrupted run).
[STEP] Installing BunkerWeb on rocky
[CMD] curl --proto =https --tlsv1.2 --fail --silent --show-error --connect-timeout 10 --max-time 60 -L https://repo.bunkerweb.io/install/script.rpm.sh -o /tmp/bunkerweb-repo.sh
curl: (23) client returned ERROR on write of 7318 bytes
[ERROR] Command failed: curl --proto =https --tlsv1.2 --fail --silent --show-error --connect-timeout 10 --max-time 60 -L https://repo.bunkerweb.io/install/script.rpm.sh -o /tmp/bunkerweb-repo.sh

BunkerWeb version

1.6.11

What integration are you using?

Linux

Linux distribution (if applicable)

Rocky OS 10

Removed private data

• I have removed all private data from the configuration file and the logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[wgh-control]

i also making clean wget from VM and download it ok:

wgh-control@justice:~$ curl --proto =https --tlsv1.2 --fail --silent --show-error --connect-timeout 10 --max-time 60 -L https://repo.bunkerweb.io/install/script.rpm.sh -o /tmp/bunkerweb-repo.sh
curl: (23) client returned ERROR on write of 7318 bytes
wgh-control@justice:~$ 
wgh-control@justice:~$ 
wgh-control@justice:~$ wget https://repo.bunkerweb.io/install/script.rpm.sh
--2026-06-24 11:24:08--  https://repo.bunkerweb.io/install/script.rpm.sh
Resolving repo.bunkerweb.io (repo.bunkerweb.io)... 51.159.125.253
Connecting to repo.bunkerweb.io (repo.bunkerweb.io)|51.159.125.253|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-sh]
Saving to: script.rpm.sh

script.rpm.sh                                      [ <=>                                                                                              ]   7.84K  --.-KB/s    in 0s      

2026-06-24 11:24:09 (121 MB/s) - ‘script.rpm.sh’ saved [8028]

[wgh-control]

[CMD] curl --proto =https --tlsv1.2 --fail --silent --show-error --connect-timeout 10 --max-time 60 -L https://repo.bunkerweb.io/install/script.rpm.sh -o /tmp/bunkerweb-repo.sh
curl: (23) client returned ERROR on write of 7318 bytes

well it looks like permission issue - if i change destination on home folder for example - it works ok

[TheophileDiot]

Hi @wgh-control, thanks for the report.

This one isn't actually a network or connectivity issue, which is why the VPN didn't change anything. The key is the curl exit code:

curl: (23) client returned ERROR on write of 7318 bytes

Exit code 23 means curl downloaded the data fine but couldn't write it to the local file (/tmp/bunkerweb-repo.sh). In almost every case this comes down to one of:

• /tmp or the root partition being full (no space left to write)
• /tmp being mounted read-only or noexec
• a permissions problem writing to /tmp

I'd also point out the line Skipping host_config phase (already completed in the interrupted run). That tells me this is a re-run after a previously interrupted install, which often leaves the disk full or in a half-finished state.

Could you run these on the VM and share the output?

df -h /tmp /
mount | grep /tmp
touch /tmp/test && echo ok && rm /tmp/test

If df shows the partition near 100%, free up some space (and clear leftovers from the interrupted run), confirm /tmp is writable, then try again.

As a side note, rather than re-running on top of a half-completed state, we recommend using the verified Easy Install script:

curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.12-rc3/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.12-rc3/install-bunkerweb.sh.sha256
sha256sum -c install-bunkerweb.sh.sha256
chmod +x install-bunkerweb.sh
sudo ./install-bunkerweb.sh

Let us know what the disk check returns and we'll go from there.