oobabooga / text-generation-webui

A Gradio web UI for Large Language Models.
GNU Affero General Public License v3.0
40.88k stars 5.34k forks source link

CSS loading from incorrect endpoint #5979

Open bars0um opened 7 months ago

bars0um commented 7 months ago

Describe the bug

I've setup text-generation-webui to run on docker using the Dockerfile and docker-compose.yaml included in the docker folder. I can launch fine and browse to localhost:7860 but the webui is all messed up. I checked the console log from the developer view, and it looks like it is trying to load the css from http://localhost/theme.css. My work around for now was to publish to both ports (7860 and 80) via an nginx reverse proxy, but I think this should be solved. Somewhere in the code the port for loading assets is not properly configured.

Is there an existing issue for this?

Reproduction

Just run as described above. Run docker compose up and connect to localhost:7860/ the theme will not load.

Screenshot

No response

Logs

I will need to reconfigure my setup to reproduce, will do if it's not obvious to fix.

System Info

I will need to reconfigure my setup to reproduce, will do if it's not obvious to fix.
bars0um commented 6 months ago

This appears to be caused by an update to gradio: https://github.com/gradio-app/gradio/issues/3472

chen150450 commented 3 months ago

For Windows Platform: Because of gradio bug and some special bug interaction. I tried each version of gradio from 4.0.0 to 4.41.0. I finally chose version 4.20.1. Modify 'requirements.txt' : gradio==4.20.1. I tested that I could use the nginx reverse proxy normally, and the extranet ports were different, and the extranet used non-standard ports. gradio模块有bug,本人使用nginx反向代理内外端口不同,也遇到同样问题,通过修改根目录下'requirements.txt'文件,把里面的gradio==xx替换成gradio==4.20.1 解决。