I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.23
Ollama Version (if applicable)
No response
Operating System
Debian GNU/Linux 12 (bookworm)
Browser (if applicable)
Firefox 142.0 (64-bit) (Windows 11)
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
> File "/app/backend/open_webui/retrieval/web/utils.py", line 477, in alazy_load
response = await page.goto(url, timeout=self.playwright_timeout)
│ │ │ │ └ 3000000
│ │ │ └ <open_webui.retrieval.web.utils.SafePlaywrightURLLoader object at 0x7f86acdbe5d0>
│ │ └ 'https://www.accuweather.com/en/de/karlsruhe/76133/weather-forecast/167218'
│ └ <function Page.goto at 0x7f86ac2b9b20>
└ <Page url='about:blank'>
Additional Information
No response
Originally created by @rawbby on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16801
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.23
### Ollama Version (if applicable)
_No response_
### Operating System
Debian GNU/Linux 12 (bookworm)
### Browser (if applicable)
Firefox 142.0 (64-bit) (Windows 11)
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
3000ms timeout
### Actual Behavior
3000000ms timeout
### Steps to Reproduce
1. Admin Panel > Web Search > Loader > Playwright Timeout (ms)
2. Run a websearch and see logs
### Logs & Screenshots
```
> File "/app/backend/open_webui/retrieval/web/utils.py", line 477, in alazy_load
response = await page.goto(url, timeout=self.playwright_timeout)
│ │ │ │ └ 3000000
│ │ │ └ <open_webui.retrieval.web.utils.SafePlaywrightURLLoader object at 0x7f86acdbe5d0>
│ │ └ 'https://www.accuweather.com/en/de/karlsruhe/76133/weather-forecast/167218'
│ └ <function Page.goto at 0x7f86ac2b9b20>
└ <Page url='about:blank'>
```
<img width="2100" height="352" alt="Image" src="https://github.com/user-attachments/assets/b821290b-ecb3-4725-a81d-ee25db501f81" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 23:57:05 -05:00
check your config, in settingsAdmin/Web_Search/Loader/Playwright Engine - Enter Playwright Timeout
<!-- gh-comment-id:3213263663 -->
@rgaricano commented on GitHub (Aug 22, 2025):
check your config, in settingsAdmin/Web_Search/Loader/Playwright Engine - Enter Playwright Timeout
I provided a screenshot showing my config, which has a value of 3000, with the label of ms. The logs show that 3000000 is passed as timeout to playwright, which i think should be milliseconds too.
Are you unable to reproduce this behaviour?
<!-- gh-comment-id:3215458411 -->
@rawbby commented on GitHub (Aug 22, 2025):
I provided a screenshot showing my config, which has a value of 3000, with the label of ms. The logs show that 3000000 is passed as timeout to playwright, which i think should be milliseconds too.
Are you unable to reproduce this behaviour?
<!-- gh-comment-id:3215504778 -->
@rgaricano commented on GitHub (Aug 22, 2025):
ok, I recheck and I found the issue, the label is incorrect , the unit is seconds. it have to say Timeout (s)
there are a conversion here:
https://github.com/open-webui/open-webui/blob/1db8dec4f52fc0fa8f8f7bfbb8ea5bde41fee17d/backend/open_webui/retrieval/web/utils.py#L617
I personally think milliseconds are a reasonable choice for the timeout. Maybe the conversion should be fixed, not the label.
This would further not break existing configurations from users that rely on their current config.
<!-- gh-comment-id:3216782565 -->
@rawbby commented on GitHub (Aug 23, 2025):
I personally think milliseconds are a reasonable choice for the timeout. Maybe the conversion should be fixed, not the label.
This would further not break existing configurations from users that rely on their current config.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rawbby on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16801
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.23
Ollama Version (if applicable)
No response
Operating System
Debian GNU/Linux 12 (bookworm)
Browser (if applicable)
Firefox 142.0 (64-bit) (Windows 11)
Confirmation
README.md.Expected Behavior
3000ms timeout
Actual Behavior
3000000ms timeout
Steps to Reproduce
Logs & Screenshots
Additional Information
No response
@rgaricano commented on GitHub (Aug 22, 2025):
check your config, in settingsAdmin/Web_Search/Loader/Playwright Engine - Enter Playwright Timeout
@rawbby commented on GitHub (Aug 22, 2025):
I provided a screenshot showing my config, which has a value of 3000, with the label of ms. The logs show that 3000000 is passed as timeout to playwright, which i think should be milliseconds too.
Are you unable to reproduce this behaviour?
@rgaricano commented on GitHub (Aug 22, 2025):
ok, I recheck and I found the issue, the label is incorrect , the unit is seconds. it have to say Timeout (s)
there are a conversion here:
https://github.com/open-webui/open-webui/blob/1db8dec4f52fc0fa8f8f7bfbb8ea5bde41fee17d/backend/open_webui/retrieval/web/utils.py#L617
@rawbby commented on GitHub (Aug 23, 2025):
I personally think milliseconds are a reasonable choice for the timeout. Maybe the conversion should be fixed, not the label.
This would further not break existing configurations from users that rely on their current config.