We Keep Coding

ntlm auth failed with error STATUS_USER_SESSION_DELETED

I am using a Windows server to manage our files(read, write). To connect to that server I am using SMB2 npm module https://www.npmjs.com/package/smb2. Internally, this module uses the ntlm method to authenticate. While authenticating, I am getting the error STATUS_USER_SESSION_DELETED. Authentication process is given below:
it sends NEGOTIATE command
SESSION_SETUP command
SESSION_SETUP command with SessionId (this is where the error is thrown)
TREE_CONNECT command
There is already open issues regarding same with Repo, so, waiting for that as well but any lead would be helpful

How to connect SSL websocket with mqtt?

I created a self signed certificate and I've been working on the mqtt websockets over SSL/TSL, however I'm unsure exactly where I made an error. On my terminal websocket is open and sends out CONNACK/SUBSCRIBE/PUBLISH etc...
However when I opened up my chrome console log, I got an error saying that
"websocket connection to 'wss:.//hostname:9001/mqtt' failed: Error in connection establishment: net: ERR_CERT_AUTHORITY_INVALID
My time is synchronised correctly, and I'm either thinking my certificate has an error or chrome doesn't accept it but if my certificate error, wouldn't it have given an error when I first tried it on regular mosquitto_sub?
Any tips?
Thank you

Connection to Redis cache failing

I have a node app connecting to a redis cache hosted on azure but whenever I'm trying to connect to it, the connection fails with an error message
I have enabled secure connection through a port and configured my node app accordingly
// This is my client module
const Redis = require("ioredis");
var client = new Redis(
{
port: 6380,
tls: true,
host: process.env.REDIS_HOST,
password: process.env.REDIS_PASSWORD,
family:
db: 0
}
);
module.exports = client;
This is the error I encounter whenever I start my app:
[ioredis] Unhandled error event: Error: unable to get local issuer certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1317:34)
at TLSSocket.emit (events.js:209:13)
at TLSSocket._finishInit (_tls_wrap.js:792:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:606:12)
The API ran for a while without any problems but then started throwing this error. My colleague is not having a problem running the same service and I'm assuming this is my machines certificates or lack of causing the issue. Any solutions or suggestions?

The problem was with the company wifi network I was using. The firewall did not allow me to connect to the cache.

An SSL certificate error occurred when fetching the script. (messaging/failed-serviceworker-registration)

I am testing my web app on localhost for firebase cloud messaging.
I am running it on a virtual host and I enabled SSL for it, I can see https but it is crossed in red. I searched and tried two methods but none of them are working
.\chrome.exe --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=https://firebase_notification.test
Also,
chrome://flags/#allow-insecure-localhost enable this flag
I am still getting the same error.
An SSL certificate error occurred when fetching the script.
get-notifications:57 An error occurred while retrieving token. FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script. (messaging/failed-serviceworker-registration).
at https://www.gstatic.com/firebasejs/6.3.4/firebase-messaging.js:1:30787

How to get NET errors in Javascript

When using WebSocket to open my wss I sometimes see in the browser console ...
foo.js:557 WebSocket connection to 'wss://:9002/changes' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID
Other times I see...
WebSocket connection to 'wss://:9002/changes' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
However, in either case the onclose event is code 1006. Is there anyway in JavaScript I can differentiate between the invalid certificate and the down connection?