[bug]: WebUI is a blank page

[PollutionPotential]

Is there an existing issue for this?

• I have searched the existing issues

OS

Windows

GPU

cuda

VRAM

4GB

What version did you experience this issue on?

3.0.0 B3

What happened?

After installing InvokeAI 3.0.0b3, I press 1 to open the webui but it's empty.
I've tried in various browsers;
Chrome based:
OperaGX (v99.0.4788.86)
OperaOne (v100.0.4815.30)
Iron (v104.0.5300.0)
Iridium (v2021.12.96.0)

Firefox based:
Firefox Nightly (v117.0a1)
LibreWolf (v114.0.2.8574)

Using the default port 9090.

CMD output:
Starting the InvokeAI browser-based UI..
A matching Triton is not available, some optimizations will not be enabled.
Error caught was: No module named 'triton'
[2023-07-08 17:35:05,315]::[InvokeAI]::INFO --> Patchmatch initialized
INFO: Started server process [11384]
INFO: Waiting for application startup.
[2023-07-08 17:35:06,059]::[InvokeAI]::DEBUG --> InvokeAI version 3.0.0+b3
[2023-07-08 17:35:06,059]::[InvokeAI]::DEBUG --> Internet connectivity is True
[2023-07-08 17:35:06,064]::[InvokeAI]::DEBUG --> config file=L:\Programs\InvokeAI\configs\models.yaml
[2023-07-08 17:35:06,064]::[InvokeAI]::DEBUG --> GPU device = cuda
[2023-07-08 17:35:06,064]::[InvokeAI]::DEBUG --> Maximum RAM cache size: 6.0 GiB
[2023-07-08 17:35:06,066]::[InvokeAI]::INFO --> scanning L:\Programs\InvokeAI\models for new models
[2023-07-08 17:35:06,314]::[InvokeAI]::INFO --> Scanning autoimport\main for models to import
[2023-07-08 17:35:06,314]::[InvokeAI]::INFO --> Scanned 0 files and directories, imported 0 models
[2023-07-08 17:35:06,314]::[InvokeAI]::INFO --> Scanning autoimport\lora for models to import
[2023-07-08 17:35:06,314]::[InvokeAI]::INFO --> Scanned 0 files and directories, imported 0 models
[2023-07-08 17:35:06,314]::[InvokeAI]::INFO --> Scanning autoimport\embedding for models to import
[2023-07-08 17:35:06,315]::[InvokeAI]::INFO --> Scanned 0 files and directories, imported 0 models
[2023-07-08 17:35:06,315]::[InvokeAI]::INFO --> Scanning autoimport\controlnet for models to import
[2023-07-08 17:35:06,315]::[InvokeAI]::INFO --> Scanned 0 files and directories, imported 0 models
[2023-07-08 17:35:06,316]::[InvokeAI]::INFO --> Model manager service initialized
[2023-07-08 17:35:06,317]::[InvokeAI]::INFO --> Face restoration disabled
[2023-07-08 17:35:06,317]::[InvokeAI]::INFO --> Upscaling disabled
[2023-07-08 17:35:06,317]::[InvokeAI]::INFO --> Face restoration initialized
INFO: Application startup complete.
INFO: Uvicorn running on http://127.0.0.1:9090 (Press CTRL+C to quit)
INFO: 127.0.0.1:63579 - "GET / HTTP/1.1" 304 Not Modified

Screenshots

No response

Additional context

No response

Contact Details

No response

[PollutionPotential]

[psychedelicious]

Thanks for testing different browsers.

Please try http://localhost:9090 - does that work?

If not, open the browser dev tools and check for any errors in the javascript console. If there are errors, please right click -> copy object and paste here.

[Feldherren]

I've been having the same issue, in both Firefox and Chrome (haven't tried anything else). Using http://localhost:9090 or http://127.0.0.1:9090 doesn't change things.
There is an error in the javascript console (output from Firefox):

Loading module from “http://localhost:9090/assets/index-f05723f9.js” was blocked because of a disallowed MIME type (“text/plain”).

[PollutionPotential]

Chrome based:
OperaOne (v100.0.4815.30)
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
http://127.0.0.1:9090/assets/index-f05723f9.js

"To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData."

OperaGX (LVL5 (core: 100.0.4815.44))
index-f05723f9.js:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.

Firefox Based:
LibreWolf (v114.0.2-1)
Loading module from “http://127.0.0.1:9090/assets/index-f05723f9.js” was blocked because of a disallowed MIME type (“text/plain”).
127.0.0.1:9090
Loading failed for the module with source “http://127.0.0.1:9090/assets/index-f05723f9.js”. 127.0.0.1:9090:15:71

[psychedelicious]

Thanks, actually just merged a fix for this: #3705

The root cause is your windows registry had its content type for JavaScript changed. So technically this is a problem on your end.

The linked fix overrides the messed up configuration on your system to ensure the web assets are served correctly.

Will be in the next release.

Edit: it's fixed in beta 4. Please update and and confirm it's working now

[PollutionPotential]

Yes, it's working on my end.
I think I know what caused the issue on my end. Seems it's a bug for Visual Studio 2019.
It's mentioned Here.

This was what fixed the issue for most there
Run the following command from an elevated command prompt: REG.EXE ADD "HKEY_CLASSES_ROOT.js" /v "Content Type" /t REG_SZ /d "application/javascript" /f

To make sure it worked
REG.EXE QUERY "HKEY_CLASSES_ROOT.js" /v "Content Type"

[psychedelicious]

In rereading my message, its kinda snarky. Was frustrated with windows, not you! Glad it's working.

[GanizaniSitara]

Yes, it's working on my end. I think I know what caused the issue on my end. Seems it's a bug for Visual Studio 2019. It's mentioned Here.

This was what fixed the issue for most there Run the following command from an elevated command prompt: REG.EXE ADD "HKEY_CLASSES_ROOT.js" /v "Content Type" /t REG_SZ /d "application/javascript" /f

To make sure it worked REG.EXE QUERY "HKEY_CLASSES_ROOT.js" /v "Content Type"

Just huge thank you - this was on a completely different software ...