Access to support

Bugs
1

Hey everyone,

I have a couple of bugs in Replit (not the application I’m building, but problems with Replit) that I’ve been waiting for support on for the last couple of weeks but not had any response. I’ve sent messages to support and the AI support bot has passed the message to the team, but I get nothing back from them.

  • “There was an unrecognized fatal error with Git. This is probably a bug in the app.” when going to the Git tab, so I cannot push to an external repo.

  • “Something went wrong, please try again.” on the project tab, so I cannot merge changes from a fork into the main Repl.

To get dedicated support you have to pay $20,000 for an enterprise license - something that’s just not possible right now.

Does anyone know of a way to contact Replit support to get things escalated? This is causing some real issues with getting my product ready for a client.

2

@kody-replit

1 Like
3

can you DM me your support ticket, will chase it down for you

2 Likes
4

Done, thanks Kody!

1 Like
5

I have never been able to get the GitHub connection to work, I read it could be due to project size 2gb limit but I don’t know. Anyone knows why I would appreciate it.

1 Like
6

Hey @jefftj86,

Support came back with this and it’s resolved my issues completely. Sharing in case it helps you:

We’ve resolved the issue by removing a corrupted config.lock file that was preventing the Project pane from loading correctly. This fix has been applied to all your affected forks, and you should now be able to access the Project tab without any errors.

Additionally, we noticed that the Git pane is showing an “Unknown Git Error” message. This is likely due to unrelated histories between your fork and the original repository. You can fix this by running the following command in your Repl’s Shell:

git merge --allow-unrelated-histories origin/main

If you encounter merge conflicts after running this command, you’ll need to:

1. Open the conflicted files in the editor

2. Look for and resolve conflict markers (<<<<<<, =======, >>>>>>>)

3. Remove these markers and keep the changes you want

4. Save the files

5. Complete the merge with:

git add .
   git commit -m "Resolve merge conflicts"
1 Like