Dynamic and static hosting not working

Bug description:
Trying to visit a Repl results in either an “unexpectedly closed the connection” or “took too long to respond” error. Randomly goes on and off, and sometimes the “–” links work while the “.” don’t. It does this dynamic and static, and sometimes says to “run this repl”

Expected vs Current Behavior:
Expected behavior is to display what the Repl is hosting

Steps to reproduce:
Visit any repl.co URL besides *.util.repl.co

Bug appears at this link:
*.repl.co

Screenshot(s)/Screen Recording:

Browser/OS/Device: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36

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

4 Likes

Yep. https://status.replit.com/ doesn’t say anything yet but this is a legitimate problem. It’s happening to several people.

2 Likes

This is the error I get when sending a request from my shell account on https://shell.oddprotocol.org:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 34.149.204.188:443...
* Connected to 9pfs.repl.co (34.149.204.188) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [315 bytes data]
* LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 9pfs.repl.co:443 

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Closing connection 0
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 9pfs.repl.co:443 

It seems to be back up.

2 Likes

Check again? It’s acting up again for me

Yeah that was short-lived.

“–” domains work, “.” ones don’t

It works for me (⊙ˍ⊙)

Never mind, “–” domains just died too

At least we had time to see that our repls are intact

2 Likes

It’s in and out it seems.

1 Like

Its now telling me to run a repl that’s already running…

Let’s stop trying to access repl.co domains, replit might be having issues with a ddos attack or something (we might be making it worse)

1 Like

Again, it’s coming in and out. That means it’s sometimes able to get through, and sometimes not. (Including when it gets confused and prompts you to run the running repl.)

1 Like

ReplIRC is somehow somewhat surviving, lol (But that’s expected)

1 Like

What’s that server again?
Edit: The element server is NOT surviving, lol.

1 Like

Which one? There’s over a dozen

uh, whichever one you’re referring to I guess, lol.

Referring to all of them… Also, there’s https://solanum.9pfs.repl.co/ (global cluster) and https://pylink.dillonb07.repl.co/ (paid cluster) (just listing two of them, too lazy to list more)

1 Like

huh. that “pylink” repl responds, “solanum” does not.