-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Unable to see project after start #728
Comments
Could you try in incognito and see if the problem persists? |
It's the same behavior. |
When the console says that there should be an alarm id (it will look similar to a Puter username for generated users). Typing something like [+] I'm testing a clone now, if that works I'm gonna try again on a Windows machine and see if that might be the issue. |
After
|
Add |
click ok, it should then bring up the login screen if my theory is accurate [+] or hopefully a different error will show up in the console at least |
I clicked ok and the alert just disappeared and no login screen appeared. And I think this is a new error:
|
Somehow it still has a session token after logging out... not sure yet how that happened. Can you check local storage and cookies and see what's in there? Clearing site data will likely fix it but it would be nice to know what's getting stuck. |
There is something named CALLED inside the console:
The APIError still is there and after the CALLED thing. I deleted the cookies and the localStorage with no change in the result, the same dark bluish screen is shown every time. |
Geez, I'm running out of ideas. I just tried a Windows computer and didn't run into this issue. Check if you have a "C:\var\puter" directory. If this exists, back it up somewhere (if you have another Puter instance that you use on this computer) and remove this directory. |
I am used to running into weird stuff that no one has ever encounter hahaha I deleted the D:\var\puter and Some lines in the console refer to the username being null somewhere, just as I start the app. This is previous to any app rendered on the browser.
[+] Is there anything that is recommended to install to run the app? Like Docker for example. |
Tbh my recommendation is WSL or Linux. We've done very little testing in Windows environments. |
When I first ran the project I had Win11, then switched to Ubuntu 24 lts and 22 lts, and now I am using Win10. In all of those OS, I had the same bold-wallet-1101 error. That's why I am asking, I will try again with WSL and see if it works. |
I would really like to reproduce this so we can get it fixed. Is there any chance you can provide a Dockerfile that reproduces the issue or a video with exact reproduction steps? |
Video context: https://vimeo.com/1005567965?share=copy I had the project forked on my github, I was executing that forked project (up to date from puter/main) and the result was the error Either way, I cannot make any changes, add files, or save anything on the localhost. Is this could be that the project doesn't have the context to save anything on the DB.
I never used docker so what do you need exactly to debug this issue? |
I wasn't able to reproduce by using a fork, I'll try later on a Windows computer. I don't notice anything in the server console that explains the error editing files. What shows up in the browser dev console? |
I can explain your observations, unfortunately none yet indicate the issue (except perhaps the socket.io error, in which case I'd expect that files do get written but you don't see new files pop up until you reload - is this accurate?)
What happens when you try to save a file? I assume there must be a console error that comes up if the save isn't successful. |
btw I tried running in a clean Ubuntu install in a VM. It works but the first time I loaded the page I got the BSOL and had to press reload to get the full gui. |
After all, my only guess is that my hardware has the issue. There are no other explanations for this bug I have. It's only happening to me, through 3 different OS, also you don't find the probable cause. |
Issue Description
After initialization with
npm start
, I am unable to use or access the app on the localhost:4100 (see screenshot 1)All the requests after opening the URL http://puter.localhost:4100/ returns status 304 (see screenshot 2)
The console also is returning some errors (see screenshot 3)
Steps to Reproduce
Unknown at the moment, I just forked the project up to date to my machine,
npm install
andnpm start
Specs: Windows 10, npm v10.8.2, node v22.5.1
Expected & Actual Behavior
After
npm start
I should see the normal page like the website puter.comAddition Information or Screenshots (if applicable)
screenshot 1
screenshot 2
screenshot 3
Deployment
npm run start
)docker run
)docker-compose
)Puter version (if accessible)
The text was updated successfully, but these errors were encountered: