MongoDB atlas stopped working on replit (Python, pymongo)

Support Bug Reports
22

again, no experience with mongo but

import pymongo, os, multiprocessing
from pymongo import errors
from urllib import request
from http import server

# minimal server for if your code isn't already serving a website before you connect to mongodb
class Server(server.BaseHTTPRequestHandler):
    # Do this to override the log_request function to prevent spammy logging output
    def log_request(_, __):
        pass

    def do_HEAD(self):
        self.send_response(204)
        self.end_headers()

    do_GET = do_HEAD


multiprocessing.Process(
    target=server.ThreadingHTTPServer(("", 80), Server).serve_forever
).start()
try:
    # connect to mongo here, e.g.
    client = pymongo.MongoClient(
        f"mongodb+srv://admin:{os.environ['db-password']}@cluster0.1shpg.mongodb.net/myFirstDatabase?retryWrites=true&w=majority"
    )
except errors.ServerSelectionTimeoutError:
    request.urlopen(f"https://{os.environ['REPL_ID']}.id.repl.co")
    os.kill(1, 1)
1 Like
23

Iā€™m now getting mongodb errors again (node.js), with Internal Server Error and Unknown system error -122. Looks like this issue wasnā€™t fully fixed and a timeframe on when this could be resolved would be great.

1 Like
24

Is there any update to this? Is it working again for anyone?

1 Like
25

No, itā€™s still a common error.

1 Like
26

This is really troublesome. Itā€™s been 15 hours and I still canā€™t connect to MongoDB with replit.

1 Like
27

Yeah, very annoying.

1 Like
28

Yep really hurts my usability of Replit

1 Like
29

I donā€™t think itā€™s an issue on Replitā€™s side. I donā€™t know for certain, but my theory is that one of Replitā€™s IPs is blacklisted from Mongo as itā€™s only an issue sometimes and kill 1 sometimes helps.

1 Like
30

I apologize for our sparse updates! We are still coordinating with our upstream providers to find the cause. I have prompted the Replit team for an update and will revert here once I get a reply.

2 Likes
31

having the same issue, itā€™s been like this for since yesterday for me. Tried connecting to a different cluster and same issue

1 Like
32

Any update or solution for this issue?

33

Welcome comjoueur, @STCollier , @cheshire1, @ThiagoGlauco , @thedankboi , @MisterNoBot , @DooM , @WTV111 , and @1Tim to the ask forum! :wave: Everyone keeps forgetting to say welcome =\

34

This Problem is A deal Breaker The Server Is Unable To Connect To the Database And itā€™s causing a lot of down time (till now mostly down time) please an urgent fix is required

3 Likes
35

Mine just started being like it today. Any updates on the problem?

1 Like
36

Weā€™re looking into this now that it has come up again, and we are able to reproduce it. We are getting in touch with an upstream service to coordinate the resolution of this issue.

2 Likes
37

Is there any temporary solution problem?

1 Like
38

Running kill 1 in the shell might fix the issue

3 Likes
39

It worked! thank you

2 Likes
40

A similar problem occurs with the replit db:

image
image2332Ɨ547 91.9 KB

I only get this error on some of my repls. kill 1 usually fixes it temporarily, but after a while the error occurs again. It looks like replit has problems with websocket connections at the moment.
Please fix these issues, they are causing a lot of downtime.

2 Likes
41

How much egress have you used? I remember that kind of issue when my account was over the egress limit (back when each free user only had 1gb of egress).

1 Like