menu
  • Register

Unchecked runtime.lasterror: could not establish connection. receiving end does not exist.

0 votes
2.1k views

Problem :

I had recently uninstalled the Postgres10 and after that reinstalled the Postgres10. After that I went to run a Node, Express, React application that relies on connecting to a Postgres10 database and also communicates with it using Sequelize.

Initially I was unable to connect it to the database. Then I realized that the uninstall process removed my old databases so then I had to recreate the new one with the name that this application is connected to. Then when I restarted the both server and client, the front-end interaction with the database was working back to normal e. g. writing new users and reading them for authentication etc.

But now I am facing the following error in the Chrome Dev Tools console on every pageload of the app:

Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist

The current error makes a reference to localhost/:1. When I try to hover over this, it shows me http://localhost:3000/, the address I am viewing the app at in the browser.

Does anyone have any idea what is going wrong? Please suggest me the solution for my error.

●6 ●5 ●3
6,930 points

Please log in or register to answer this question.

1 Answer

0 votes

Solution :

For Chrome Browser:

1. You have your chrome browser window open with the console error, please open up a second new chrome browser window.

2. In the second new chrome browser window, please go to: chrome://extensions

3. Here please Disable each extension by toggling and refresh the new chrome browser window with the console after toggling each of the extension.

4. Once you see that you don't have the error anymore just remove the extension.

5. Now your issue is resolved

●9 ●7 ●4
38,600 points

Related questions

0 votes
1 answer 156 views
156 views
Unchecked runtime.lasterror: could not establish connection. receiving end does not exist .
Problem: Facing this error message: Unchecked runtime.lasterror: could not establish connection. receiving end does not exist.
asked Mar 14 Wafa Abu Yousef 6.1k points
0 votes
2 answers 2.6K views
2.6K views
Unchecked runtime.lasterror: the message port closed before a response was received.
Problem : Currently I am using VueJS and Laravel for the project. Following issue started to show lately and it also comes up even in the old git branches. Unchecked runtime.lasterror: the message port closed before a response was received. This error only comes up in Chrome browser.
asked Dec 10, 2019 alecxe 7.5k points
0 votes
1 answer 8 views
8 views
Unexpected end of json input while parsing near
Problem: the Error is npm ERR! **Unexpected end of JSON input while parsing near '...nt-webpack-plugin":"0'**
asked Mar 16 ummesalma 29.2k points
0 votes
1 answer 21 views
21 views
npm err! unexpected end of json input while parsing near
Problem npm err! unexpected end of json input while parsing near.
asked Feb 24 Dan phillip 4.8k points
0 votes
1 answer 5 views
5 views
1 vulnerability required manual review and could not be updated
Problem: When I run npm install it says found 33 vulnerabilities (2 low, 31 moderate) run `npm audit fix` to fix them, or `npm audit` for details.However, npm audit fix outputs up to date in 11s fixed 0 of 33 vulnerabilities in 24653 scanned packages 33 vulnerabilities required manual review and could not be updated.Does that review mean it is not supposed to be fixed by user?
asked May 4 sumaiya simi 43.9k points
0 votes
1 answer 874 views
874 views
Error: could not symlink share/doc/node/gdbinit /usr/local/share/doc/node is not writable.
Problem : I made the big mistake of trying remove all sudo dependencies. I simply downloaded npm as a package from the preferred site and did a manual global install. But I had to always run with the sudo. That's why I tried to uninstall and tried to run it with homebrew. ... once built. Run `brew link` on these: Now I am completely stuck and don't know how to solve it. Does anybody have any clue?
asked Nov 25, 2019 alecxe 7.5k points
0 votes
1 answer 242 views
242 views
node sass could not find a binding for your current environment: os x 64-bit with node.js 8.x
Problem : I am facing issues while building an app as node-sass keeps giving the following error : node sass could not find a binding for your current environment: os x 64-bit with node.js 8.x
asked Nov 15, 2019 peterlaw 6.9k points
0 votes
0 answers 7 views
7 views
User "root" does not have permission to access the dev dir
Problem: user "root" does not have permission to access the dev dir
asked Feb 19 Dan phillip 4.8k points
0 votes
1 answer 229 views
229 views
Client does not support authentication protocol requested by server consider upgrading mysql client
Problem : I am very new to node.js and MySQL and I have just started setting up and also trying out some basic code. But, I am unable to make even the simple connection to a server for some reason. I have also installed a newest MySQL ... ; console.log("Connected!"); }); My Error: “Client does not support authentication protocol requested by server consider upgrading mysql client”
asked Jan 30, 2020 jwilliam 3.9k points
0 votes
1 answer 459 views
459 views
Upstream prematurely closed connection while reading response header from upstream
Problem : Currently I am using the nginx and node server to serve the update requests. I often face the gateway timeout whenever I request an update on large data. I saw below error from the nginx error logs as below : 2019/04/07 00:46:04 [error] 28599#0: *1 upstream ... time around 3-4 minutes. Please note I do not get the error for smaller updates. Please let me know how can I resolve the issue.
asked Dec 18, 2019 alecxe 7.5k points
Dark theme