New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black screen on fresh install #513
Comments
same here |
Also having this problem |
For now, you can just downgrade the version sudo npm -g install wetty@2.6.0 Works for me. |
same issue here |
Running Wetty from source on my machine also results in a black screen. |
Same issue here. Tried downgrading with no result. It complains (in firefox javascript console) that "Uncaught TypeError: Error resolving module specifier “@fortawesome/fontawesome-svg-core”. Relative module specifiers must start with “./”, “../” or “/”." but the fontawesome modules are installed (npm i --save @fortawesome/fontawesome-svg-core) so... clueless. |
Additional note: i have installed on bare metal, no docker. |
Same issue here |
Thanks, brooo |
We're encountering a very similar issue with 2.7.0 running on Ubuntu 23.04. During the time that it is not working, we've noticed that it pegs the CPU at 100%. This continues for anywhere from two to fifteen minutes and then it recovers. When the CPU drops back down, Wetty again responds. Throughout the entire time a web request to the "home" page will work, but files referenced from there (js, css) will not, hence a "black" or "white" page without any functionality. We've downgraded to version 2.6.0 and are now testing... Unfortunately, the downgrade had no apparent impact. We still see the same behavior. |
seems to fix with a downgrade. |
Rebuilding my old docker with wetty. Working fine before, not now
To Reproduce
Built with this Dockerfile :
tested with yarn or npm install, same result
If I make a cURL I got a response :
If I test opened ports on the container :
So, wetty is up, but screen still black :
Tested on Firefox, Edge and K-meleon
The text was updated successfully, but these errors were encountered: