Skip to content
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

repl.it: Blank white screen after about 30 seconds Webpage: reloads the REPL #35

Closed
24tiptlo opened this issue Dec 7, 2022 · 4 comments

Comments

@24tiptlo
Copy link

24tiptlo commented Dec 7, 2022

My deployment is on replit. For some reason, after clicking "Run", it would work completely fine for about 30 seconds where it would do two different things depending on what you were using:

On the Replit "Web View" window, it would display a blank white screen before showing the little replit robot and a loading bar.

On the actual webpage, it would stop loading certain things (like the twitter view, for example). And when you tried to refresh, it would try to awake the REPL.

sometimes on both, it would load multiple robots.

Screenshot 2022-12-07 4 48 15 PM
Screenshot 2022-12-07 4 47 56 PM
Screenshot 2022-12-07 4 47 45 PM

It should be noted that this happened after I updated the fork.

I have tried updating the dependencies using npm update as well as npm audit fix. I have also tried using one of my forks.

I am however not getting many errors.

I say many because once, I got an error saying it couldn't find a 404.html, and another time I got an error about the bare server node, however I haven't been able to recreate them.

@24tiptlo
Copy link
Author

24tiptlo commented Dec 7, 2022

I would also like to point out that https://website-aio-e9x.koyeb.app/ isn't working, as well as https://website-aio.herokuapp.com/. although, I can understand the herokuapp one is down because I heard they removed free dynos in issue #34

@e9x
Copy link
Collaborator

e9x commented Dec 8, 2022

This has something to do with how we start Rammerhead. You have timed the issue to be 30 seconds, exactly the amount of time we wait before starting rammerhead.

@e9x
Copy link
Collaborator

e9x commented Dec 8, 2022

This was fixed by listening on only one port, which requires running Rammerhead in the same process as the Bare server and the static webserver.
ba03073.

@e9x e9x closed this as completed Dec 8, 2022
@e9x
Copy link
Collaborator

e9x commented Dec 8, 2022

I would also like to point out that https://website-aio-e9x.koyeb.app/ isn't working, as well as https://website-aio.herokuapp.com/.

The service isn't active due to the Railway account's inactivity. We will need to use a combination of CI and self-hosting to demo website-aio.
And yes, Heroku has removed free dynos, which would explain why our official Heroku deployment is down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants