mirror of
https://github.com/SillyTavern/Extension-WebLLM.git
synced 2026-10-15 13:31:50 +00:00
[GH-ISSUE #3] WebGPU not supported in your current environment? #1
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/Extension-WebLLM#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jtabox on GitHub (Nov 17, 2025).
Original GitHub issue: https://github.com/SillyTavern/Extension-WebLLM/issues/3
Hi, since about a week ago, WebLLLM has stopped working. Every time I try to test it, or some extension tries to use it, it shows an error message that WebGPU is not supported in the browser.
Which isn't the case, I use the latest Chrome in Windows with an NVIDIA 3090 card. Also checking in webgpureport.org says that my browser supports WebGPU, so I assume it's WebLLM that doesn't see it?
I've reinstalled it but it didn't make any difference.
Any suggestions would be greatly appreciated because I really don't know what I can do.
@Cohee1207 commented on GitHub (Nov 17, 2025):
I've seen a recommendation to enable the "Force High Performance" flag in Chrome.
@jtabox commented on GitHub (Nov 18, 2025):
I found the reason, though I'm not exactly sure how it matters, I guess some browser stupid security thing: My SillyTavern instance runs in a Docker container, and I configured it recently so that it is accessible from other devices in my LAN. But if I open SillyTavern's start page with
http://10.0.10.1:8000(my PC's LAN IP) from the same PC it runs, WebGPU won't work and throws the above error. If I open the same page, from the same browser but aslocalhost:8000, the problem disappears. Not sure what the connection is, but in any case the issue is resolved.Thanks for replying :)
@Cohee1207 commented on GitHub (Nov 18, 2025):
Yeah, that's likely the case. WebGPU requires secure context: either localhost, or HTTPS.