Replit is still not working

Support Bug Reports
1

Bug description:
Repls Still not working after the recent fix
Its just loading Forever then says “We ran into an internal error.”

Expected vs Current Behavior:
Repl should load fine without any problem

Steps to reproduce:
Create a project thats not html

Bug appears at this link:
https://

Screenshot(s)/Screen Recording:
image

Browser/OS/Device: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36

Replit Profile: https://replit.com/@jaydogstack

2

Hey @jaydogstack! Welcome to the community!

You will need to create a web server in your Repl in order to create a website from your Repl. Otherwise, this page will appear.

3 Likes
3

I don’t really get what you said. I’m kind of new to this stuff. Could You explain this in easier terms

4

Your Repl needs to host a website for a website to appear. However, you did not provide the link to your Repl, so determining the best way to host a website could be tricky.

5

This website was working fine before the status error. Even after you supposedly fixed it?

6

I didn’t claim to fix it and you still provided no useful links. You can’t expect help without providing a proper explanation of the problem.

7

not again … what is going on on replete. This said, I have no issue here

8

sorry, but the link was https://aaaaaaaaaa-2.jaydogstack.repl.co/ and it doesnt work all a sudden

9

Is your Repl private?
https://replit.com/@jaydogstack/aaaaaaaaaa-2

10

Yes my Repl was private

11

We can’t help you very much without a code to review.

12

I can make it public if you need me to

13

That would help everyone here.

14

Alright i made it public

15

Unless you tweaked a hidden file, you need your server to run on index.js not server.js.

16

I put the code from server.js into index.js but i am still getting the same error

17

You have to run the Repl again.

18

Alright I stopped it then ran it again. Still the same Error, This also happens to most of my repls

19

It’s possible that hosting is down again.

20

Alright thanks for the help