Not able to see login page
See original GitHub issueDescribe the bug
I’m following the instruction and run docker run --rm -p 3000:3000 wettyoss/wetty --ssh-host=<YOUR-IP>
, but cannot see the login page, only a black page shown.
There are some error from browser console:
Navigated to http://localhost:3000/wetty
wetty.js:1 GET http://localhost:3000/wetty/_snowpack/pkg/lodash.js net::ERR_ABORTED 404 (Not Found)
wetty.js:2 GET http://localhost:3000/wetty/_snowpack/pkg/@fortawesome/fontawesome-svg-core.js net::ERR_ABORTED 404 (Not Found)
wetty.js:3 GET http://localhost:3000/wetty/_snowpack/pkg/@fortawesome/free-solid-svg-icons.js net::ERR_ABORTED 404 (Not Found)
Anything wrong or missed?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Fixed: No Login Screen Error on Windows 10 | SoftwareKeep
Guide to fixing the no login screen error · Method 1: Restart your computer · Method 2: Try Ctrl + Alt + Delete...
Read more >I can't log in to a website - WhatIsMyBrowser.com
Probably the most common cause of not being able to log in to a website is using the wrong password. At least websites...
Read more >Fix login issues on websites that require a username and ...
Fix login issues on websites that require a username and password · Enable cookies for the website · Clear history for that site...
Read more >[Solved] No Login Screen in Windows 10 | Quickly & Easily
Fix 1: Try Ctrl + Alt + Delete combinations · On the locked screen where you can't see the login screen, press any...
Read more >To Do doesn't show login window after pressing Sign In
Here's how to do it: On the locked screen where you can't see the login screen, press any key or click the screen...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like at some point
web_modules
was renamed to_snowback
in the build. Updating the server to serve this path should fix the issueYou have to git clone, then npm install /home/user/wetty then yarn add /home/user/wetty then npm run build that will create the build directory where you will see the files and for executing you have to do node /home/user/weety/build/main.js