DominikDoom/a1111-sd-webui-tagcomplete

Fork 0

mirror of https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git synced 2026-11-05 00:17:25 +00:00

[GH-ISSUE #1] config.json can't load #3

New issue

Closed

opened 2026-10-30 21:16:42 +00:00 by bsakaguchi · 7 comments

bsakaguchi commented

2026-10-30 21:16:42 +00:00

Owner

Originally created by @gdtiti on GitHub (Oct 11, 2022).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/1

http://127.0.0.1:7860/file/tags/config.json 500 internal server error

Originally created by @gdtiti on GitHub (Oct 11, 2022). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/1 http://127.0.0.1:7860/file/tags/config.json 500 internal server error

bsakaguchi

2026-10-30 21:16:42 +00:00

closed this issue
added the
waiting for feedback
label

bsakaguchi commented

2026-10-30 21:16:43 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 11, 2022):

Did you place the file in the right spot? I tested it on Chrome and Firefox just now and it still works for me.

@DominikDoom commented on GitHub (Oct 11, 2022): Did you place the file in the right spot? I tested it on Chrome and Firefox just now and it still works for me.

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@evanjs commented on GitHub (Oct 15, 2022):

I'm seeing a similiar issue with any files specified in wc.txt.

The wc.txt file appears to initialize as expected, but reads for the specified files seem to fail.

It looks like there is some sandboxing, and only certain files are allowed to load, as far as I can tell.

ValueError: File cannot be fetched: scripts/wildcards/views.txt, perhaps because it is not in any of
{'C:\\Users\\evanjs\\AppData\\Local\\Temp\\tmp1z27z66v', 'C:\\Users\\evanjs\\AppData\\Local\\Temp\\tmpfnroftve', ... }

Source of upstream error:
github.com/gradio-app/gradio@831ae1405f/gradio/routes.py (L253-L256)

@evanjs commented on GitHub (Oct 15, 2022): I'm seeing a similiar issue with any files specified in `wc.txt`. The `wc.txt` file appears to initialize as expected, but reads for the specified files seem to fail. It looks like there is some sandboxing, and only certain files are allowed to load, as far as I can tell. ``` ValueError: File cannot be fetched: scripts/wildcards/views.txt, perhaps because it is not in any of {'C:\\Users\\evanjs\\AppData\\Local\\Temp\\tmp1z27z66v', 'C:\\Users\\evanjs\\AppData\\Local\\Temp\\tmpfnroftve', ... } ``` Source of upstream error: https://github.com/gradio-app/gradio/blob/831ae1405f0f2cddf8d508775731eef39c5a09df/gradio/routes.py#L253-L256

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 15, 2022):

Yes, Gradio for security reasons only allows to load files in the app root and its subdirectories via JavaScript. But everything in the wildcards folder should be fine under that condition.
Are you running the webui from a different location or something like that?

@DominikDoom commented on GitHub (Oct 15, 2022): Yes, Gradio for security reasons only allows to load files in the app root and its subdirectories via JavaScript. But everything in the wildcards folder should be fine under that condition. Are you running the webui from a different location or something like that?

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@evanjs commented on GitHub (Oct 15, 2022):

Thanks for the 🦆, that makes sense now.
I have wildcards stored somewhere external to the webui, and that is what was causing issues on my end.
Ensuring any/all symlinks point to a directory within the application root ensures that the wildcard files can be loaded properly.

@evanjs commented on GitHub (Oct 15, 2022): Thanks for the 🦆, that makes sense now. I have wildcards stored somewhere external to the webui, and that is what was causing issues on my end. Ensuring any/all symlinks point to a directory within the application root ensures that the wildcard files can be loaded properly.

bsakaguchi commented

2026-10-30 21:16:44 +00:00

Author

Owner

@martinobettucci commented on GitHub (Nov 17, 2022):

I have the same problem since installing the extension via the installer manager from auto1111.
It works if I copy the extension manually into the root

@martinobettucci commented on GitHub (Nov 17, 2022): I have the same problem since installing the extension via the installer manager from auto1111. It works if I copy the extension manually into the root

bsakaguchi commented

2026-10-30 21:16:45 +00:00

Author

Owner

@DominikDoom commented on GitHub (Nov 17, 2022):

@martinobettucci Can you tell me a few more details? Is there an error message in the command prompt running the webui?
Also, if you used the legacy version before installing it from the manager, make sure to move/delete all script parts of it (see #76) so that there is no remnant still using old non-extension paths.

@DominikDoom commented on GitHub (Nov 17, 2022): @martinobettucci Can you tell me a few more details? Is there an error message in the command prompt running the webui? Also, if you used the legacy version before installing it from the manager, make sure to move/delete all script parts of it (see #76) so that there is no remnant still using old non-extension paths.

bsakaguchi commented

2026-10-30 21:16:45 +00:00

Author

Owner

@DominikDoom commented on GitHub (Jan 10, 2023):

Since the original issue was ages ago before the extension system, and the OP has not provided feedback, closing the issue for now.

@DominikDoom commented on GitHub (Jan 10, 2023): Since the original issue was ages ago before the extension system, and the OP has not provided feedback, closing the issue for now.

bsakaguchi referenced this issue

2026-10-30 21:21:32 +00:00

[PR #3] [MERGED] Fix input event #236