This is only occurring when I'm on a VPN on my Win 7 machine. Outside VPN, on any public or private wifi connection, everything runs fine.
C:\node\ultronnode2\node_modules\mongoose\node_modules\mongodb\lib\server.js:228
process.nextTick(function() { throw err; })
^
Error: getaddrinfo ENOTFOUND dsXXXXXX.mongolab.com
at errnoException (dns.js:44:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:94:26)
Any idea how can I connect my Express app with Mongolab over VPN?
Thanks in advance.
Related
I am using Node v18.12.1 and vite v3.0.4. Below is my proxy code to connect to a Node.js REST API from the Vue.js vite dev server:
proxy: {
"/api": {
target: "http://localhost:3000",
changeOrigin: true,
}
}
After updating my node version from v16 I now get this error from vite-proxy:
[vite] http proxy error:
Error: connect ECONNREFUSED ::1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) (x3)
I have heard that sine v17, Node favours ipv6 for localhost. How do I fix this?
You could run the service you are trying to connect to on ::1 or configure your proxy target to use the IPv4 address (http://127.0.0.1:3000).
I have a Blazor App that runs perfectly well on localhost, however, when I deploy it to the server I get the following error:
Error: Failed to complete negotiation with the server: Error: Forbidden
Error: Failed to start the connection: Error: Forbidden
Error: Error: Forbidden
Error: Cannot send data if the connection is not in the 'Connected' State.
error comes from blazor.server.js.
I looked everywhere and there is no such error reported as far as I know.
Turns out, firewall was blocking it. Simply changing it's security to a lower level did the trick
I am trying to open my app and it doesn't apear.
I only get this error message.
Uncaught Error: java.net.SocketTimeoutException: failed to connect to /192.168.56.1 (port 19000) from /192.168.1.232 (port 55968) after 10000ms
This problem is since i changed my cellphone, but i got the app also on my new one.
I am trying to connect Raspberry Pi using TLS with Client Certificate and Token to Watson IoT Platform and after following this tutorial :
https://developer.ibm.com/recipes/tutorials/connect-raspberry-pi-to-ibm-watson-iot-platform-using-client-side-certificates/
I had this this issues :
[BaseClient:connect] Connecting to IoTF with host : ssl://XXXXX.messaging.internetofthings.ibmcloud.com:8883
[BaseClient:onError] Connection Error :: Error: Connection refused: Not authorized
Error: Connection refused: Not authorized
at MqttClient._handleConnack (/home/pi/node_test_watson/iot-nodejs/node_modules/mqtt/lib/client.js:673:9)
at MqttClient._handlePacket (/home/pi/node_test_watson/iot-nodejs/node_modules/mqtt/lib/client.js:274:12)
at process (/home/pi/node_test_watson/iot-nodejs/node_modules/mqtt/lib/client.js:218:12)
at Writable.writable._write (/home/pi/node_test_watson/iot-nodejs/node_modules/mqtt/lib/client.js:228:5)
at doWrite (/home/pi/node_test_watson/iot-nodejs/node_modules/readable-stream/lib/_stream_writable.js:237:10)
at writeOrBuffer (/home/pi/node_test_watson/iot-nodejs/node_modules/readable-stream/lib/_stream_writable.js:227:5)
at Writable.write (/home/pi/node_test_watson/iot-nodejs/node_modules/readable-stream/lib/_stream_writable.js:194:11)
at TLSSocket.ondata (_stream_readable.js:555:20)
at emitOne (events.js:96:13)
at TLSSocket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at TLSSocket.Readable.push (_stream_readable.js:134:10)
at TLSWrap.onread (net.js:548:20)
[BaseClient:connect] Iotfclient is offline. Retrying connection
[BaseClient:connect] Retry in 3 sec. Count : 1
[BaseClient:onClose] Connection was closed.
Disconnected from IoTF
what can i do plaese ??
I am running a simulator which establishes SSL connections and sends HTTP requests.
But currently when I run the simulator I get below error:
ERROR: SSL_CTX_use_certificate_file failed ERROR: [SSL#906d06c]
error:0906D06C:PEM routines:PEM_read_bio:no start line ERROR:
[SSL#140ad009] error:140AD009:SSL
routines:SSL_CTX_use_certificate_file:PEM lib ERROR: Global SSL
initialization failed
Could anyone help me solve this issue?