-
Notifications
You must be signed in to change notification settings - Fork 180
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
Infinite Loading? #17
Comments
Hi! I'm sorry for the bad experience 😔. Theoratically, you can always visit the https://creator.nolibox.com/guest link, without the local deployment... So if you encountered infinite loading, it might be a bug of our frontend, but not your local deployment procedure. So can you open the browser's console after the infinite loading and make a screenshot for me? Thanks! |
Hi! Seems that it does need to turn off your VPN 😆 (It happens because of some messy CDN stuffs). I'm happy that the UI loads for you, and I'm also looking forward to your precious advice and suggestions! |
Hi, how do you solve local Infinite Loading,I'm having the same problem with docker builds as you |
Does your infinite loading happen with the UI, or with the generation process? |
Hello! Been looking forward to trying this webui, but having some trouble getting it running.
I've tried both the Google collab solution and local deployment and seem to get a similar issue with both.
After the running all the setup in the google collab up until the part where the message "Server is ready!" I open the link to https://creator.nolibox.com/guest and the menus on both right and left sides just load infinitely. There are no options I can interact with there.
I tried the local deployment solution as well, but I seem to be stuck endlessly after idm_semantic finishes. After having tried multiple times, I seem to always be stuck there for more than an hour without anything happening.

I managed to solve previous issues using the information already provided, but I am at a loss if there is simply no error message.
The text was updated successfully, but these errors were encountered: