Err address invalid как исправить

Well not really, this modification is usually only needed in the front-end if you are able to see the explorer http://127.0.0.1:3000/explorer then it is possible that the real-time component is not running. But you can always try. TIP: also whatever config you set in the backend, will be generated in the front-end when you create the SDK.

You can make sure the real-time component is running by enabling the debug mode

server/component-config.json

{
  "loopback-component-explorer": {
    "mountPath": "/explorer"
  },
  "@mean-expert/loopback-component-realtime": {
    "auth": false,
    "debug": true
  }
}

and you should see something like:

@mean-expert/loopback-component-realtime: RTC authentication mechanism enabled
@mean-expert/loopback-component-realtime: PubSub server enabled using socket.io driver.
@mean-expert/loopback-component-realtime: IO server enabled using socket.io driver.
@mean-expert/loopback-component-realtime: FireLoop server enabled using socket.io driver.
@mean-expert/loopback-component-realtime: WebRTCSignaler server enabled using socket.io driver.
Web server listening at: http://0.0.0.0:3000
Browse your REST API at http://0.0.0.0:3000/explorer

Also, if you open the following link what is the result?

a ) It downloads a file with handshake information
b ) It does return a not found page 404

This evening I discovered that I could not access any websites from Chrome, Firefox, etc. At first I though my router might just need rebooting, but I quickly found that I had no trouble tracerouteing to e.g. google.com.

Furthermore, if I telnet to www.google.com port 80 it connects, and GET / returns a web page. Other machines on the same network have no connectivity problems, so it seems specific to this one Mac.

What is wrong with networking such that Chrome and Firefox refuse to connect, but I can access things fine with command line tool. And how can I fix it?

Update: I get the same ERR_ADDRESS_INVALID when I try to point Chrome to http://74.125.224.193, which is what dnslookup on the same machine gives as one of Google’s IP addresses. What exactly does this error mean, since obvious this address is not, in and of itself, «invalid».

Second update: after about 5 minutes, the above address suddenly brings up Google’s web page. But I try another web site by IP and it gives the same ERR_ADDRESS_INVALID.

Third update: After about 30 minutes of trying various things I finally gave up and rebooted the machine. This fixed the problem. However, I still would like to know what the problem was, and if it is possible to fix it without rebooting. It seems to be a rather disturbing trend that Mavericks is more prone to needing a reboot than earlier versions of OS X.

This evening I discovered that I could not access any websites from Chrome, Firefox, etc. At first I though my router might just need rebooting, but I quickly found that I had no trouble tracerouteing to e.g. google.com.

Furthermore, if I telnet to www.google.com port 80 it connects, and GET / returns a web page. Other machines on the same network have no connectivity problems, so it seems specific to this one Mac.

What is wrong with networking such that Chrome and Firefox refuse to connect, but I can access things fine with command line tool. And how can I fix it?

Update: I get the same ERR_ADDRESS_INVALID when I try to point Chrome to http://74.125.224.193, which is what dnslookup on the same machine gives as one of Google’s IP addresses. What exactly does this error mean, since obvious this address is not, in and of itself, «invalid».

Second update: after about 5 minutes, the above address suddenly brings up Google’s web page. But I try another web site by IP and it gives the same ERR_ADDRESS_INVALID.

Third update: After about 30 minutes of trying various things I finally gave up and rebooted the machine. This fixed the problem. However, I still would like to know what the problem was, and if it is possible to fix it without rebooting. It seems to be a rather disturbing trend that Mavericks is more prone to needing a reboot than earlier versions of OS X.