[BUG] 500 error when accessing Web Bans page

[bowtiesolutions]

[BUG] 500 error when accessing Web Bans page

[fl0ppy-d1sk]

Hello @bowtiesolutions,

Looks like I can't reproduce the issue.

Here is what I did :

1. Install BW 1.5.6 on Ubuntu 22.04 : https://docs.bunkerweb.io/1.5.6/integrations/#linux
2. Complete the setup wizard with a valid domain
3. Access the ban page

Can you confirm that you installed the 1.5.6 version and not a dev/testing one ?

[bowtiesolutions]

Yes, have checked and confirmed 1.5.6 is in use and that both bunkerweb and nginx are held at their installed versions per the integration instructions.

I can't confirm I was able to access the bans page previously, however I was able to use 'bwcli bans' however am no longer able to (see below).

[2024-05-13 01:11:40] - API - ❌ - Can't send API request to http://127.0.0.1:5000/bans : Request failed: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /bans (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1ba1c83430>: Failed to establish a new connection: [Errno 111] Connection refused')) [2024-05-13 01:11:40] - CLI - ❌ - Error while executing bwcli : Traceback (most recent call last): File "/usr/share/bunkerweb/cli/main.py", line 66, in <module> ret, err = cli.bans() File "/usr/share/bunkerweb/cli/CLI.py", line 246, in bans ret, resp = self.send_to_apis("GET", "/bans", response=True) TypeError: cannot unpack non-iterable bool object

[fl0ppy-d1sk]

Hello @bowtiesolutions,

Can you try again with the new 1.5.7 version ? More info here : https://docs.bunkerweb.io/1.5.7/

[bowtiesolutions]

I ended up doing a clean reinstall to 1.5.7 as the update process did not complete normally and my configuration was lost.

The bans page and bwcli are now responding normally. Running sudo netstat -nlp shows the API endpoint loaded now, this was not the case for 1.5.6.

tcp 0 0 127.0.0.1:5000 0.0.0.0:* LISTEN 4427/nginx: master

I suspect that /etc/nginx/api.conf was not being correctly generated or referenced in my previous installation leading to the error.