[Bug] Web interface doesn't respond after 10 reloads

[adm2d]

Before submitting
☑️ I checked Known Issues
☑️ I searched existing issues

Configuration
gpt4free version: 6.7.1

services:
  g4f:
    image: hlohaus789/g4f:latest-slim
    container_name: gpt4free
    ports:
      - "1337:8080"
      - "7900:7900"
      - "8081:8080"
    environment:
      - HTTP_PROXY=http://proxyaddr:8119
    volumes:
      - ./har_and_cookies:/app/har_and_cookies
      - ./generated_media:/app/generated_media
    restart: unless-stopped

• Model: any
• Provider: any
• Interface:Web UI

Bug description
Clear steps to reproduce:

1. Open in browser: http://192.168.1.100:8119/chat/
2. Refresh page 10 times
3. Observed behavior:
   Any Gpt4free pages stop responding completely until restarting docker container.
   Nor I can reach interface in a new page
4. It is not required to hit F5 10 times in a row but enough open the interface in a spread of time. I noticed it when the service regularly stopped responding.
5. If interface responds the curl command curl -v http://192.168.1.100:8081/chat/ doesn't break service and it responds normally until somebody open web page 10 times

Environment

• OS: Debian 13
• Docker version 29.1.3, build f52814d

Screenshots/Logs
There is nothing unusual in the logs at all during the incident:

gpt4free  | Already up to date.
gpt4free  | UPDATE: #1
gpt4free  | From https://github.com/xtekky/gpt4free
gpt4free  |  * branch              main       -> FETCH_HEAD
gpt4free  | Already up to date.
gpt4free  | UPDATE: a2
gpt4free  | From https://github.com/xtekky/gpt4free
gpt4free  |  * branch              main       -> FETCH_HEAD
gpt4free  | Already up to date.

When interface stops responding curl doesn't receive any response as well

curl -v http://192.168.1.100:8081/chat/                                                                                                                                                                                                                                                                          
*   Trying 192.168.1.100:8081...
* Established connection to 192.168.1.100 (192.168.1.100 port 8081) from 192.168.1.155 port 42890 
* using HTTP/1.x
> GET /chat/ HTTP/1.1
> Host: 192.168.1.100:8081
> User-Agent: curl/8.17.0
> Accept: */*
> 
* Request completely sent off

Additional context
I use http proxy but it presence or absence doesn't affect the bug.

[github-actions]

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

[adm2d]

Is there any chance that you will confirm the bug or say that there is no bug and I have configured something incorrectly? Since I'm still dealing with the service hanging up, I don't know how to fix it other than restarting the docker container regularly.