wandb / openui

OpenUI let's you describe UI using your imagination, then see it rendered live.
https://openui.fly.dev
Apache License 2.0
19.26k stars 1.78k forks source link

accessing 127.0.0.1:7878 open blank page (windows 11 - AMD) #79

Open cksbisqui opened 6 months ago

cksbisqui commented 6 months ago

Hello. I have follow the instructions to the dot, and everything installed ok. Created an openui environment, did pip install, set my openai key, and once server is up, I get a blank page. Please help!

in the cmd I get this:

(openui) F:\OpenUIfolder\openui\backend>python -m openui wandb: Unpatching OpenAI completions INFO (openui): Starting OpenUI AI Server created by W&B... INFO (openui): Running API Server INFO (uvicorn.error): Started server process [22552] INFO (uvicorn.error): Waiting for application startup. DEBUG (openui): Starting up server in 22552... INFO (uvicorn.error): Application startup complete. INFO (uvicorn.error): Uvicorn running on http://127.0.0.1:7878 (Press CTRL+C to quit) INFO (uvicorn.access): 127.0.0.1:53891 - "GET /ai/new HTTP/1.1" 200 INFO (uvicorn.access): 127.0.0.1:53891 - "GET /assets/index-6BqEBdFF.js HTTP/1.1" 200 INFO (uvicorn.access): 127.0.0.1:53892 - "GET /assets/vendor-BGjp6CLF.js HTTP/1.1" 200 INFO (uvicorn.access): 127.0.0.1:53893 - "GET /assets/index-DspDvSlJ.css HTTP/1.1" 200

Screenshot 2024-05-04 233530 Screenshot 2024-05-04 234712 Screenshot 2024-05-04 234802

vanpelt commented 6 months ago

The errors are saying the JavaScript files are returning plain text. Can you share what's being returned by selecting one of the js files from the last screenshot you shared?

Fahadxx commented 6 months ago

I'm facing the same issue, windows 10

cksbisqui commented 6 months ago

@vanpelt , Thank you for helping out with the issue. Here are the screenshots. the .js are empty, all of them, and in the 127.0.0.1, I see this in the second screenshot. I searched and found out some comments about React and a specific line in the code, <script type="module" crossorigin src="/assets/index-6BqEBdFF.js"></script> , that should have <script type="text/javascript" ...> instead. But I don't know if that is the issue here, and I cannot change that code in the browser to test it.

Screenshot 2024-05-06 150232 Screenshot 2024-05-06 150339

I was able to build it on docker, but then it was not finding Ollama, and my first task made the process freeze up.

vanpelt commented 6 months ago

It could be a windows path issue. I'll try it in Windows when I get a chance.

k2an commented 6 months ago

sadly same error on my side. any solution will be great.

magdymaher2024 commented 6 months ago

I' am facing same error in windows 10 also

Ereis commented 6 months ago

Same issue on windows 11

VCDragoon commented 5 months ago

Did anyone ever figure this out? I'm getting this same error on Windows 11

cksbisqui commented 5 months ago

@vanpelt , were you able to have a look at this issue? Much appreciated.

vanpelt commented 5 months ago

Haven't had access to a windows machine. Short term quick solution is to just run it in docker, I'll be publishing an official image soon. I'll try to take a look, for anyone adventurous, the problem code for windows is probably here. A quick and dirty fix might be to do something like:

if os.name == "nt":
  full_path = full_path.replace("/", "\")
cksbisqui commented 5 months ago

Thank you for the reply @vanpelt.

Cheers.

On Jun 6, 2024 at 6:54 PM, Chris Van Pelt @.***> wrote:

Haven't had access to a windows machine. Short term quick solution is to just run it in docker, I'll be publishing an official image soon. I'll try to take a look, for anyone adventurous, the problem code for windows is probably here. A quick and dirty fix might be to do something like:

if os.name == "nt": full_path = full_path.replace("/", "\")

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>