I recently came across an error stating that there's apparently a self signed certificate in certificate chain and I had absolutely no issue with the command its originating from before. The command it's originating from is a fact.js command. The code is:
const {Discord, richEmbed} = require('discord.js')
const neko = new client();
module.exports = {
name: "fact",
category: "fun",
description: "sends a cool fact",
usage: "[command]",
run: async (client, message, args) => {
async function work() {
let owo = (await neko.sfw.fact());
message.channel.send(owo.fact).catch(error => {
console.error(error);
});
message.delete();
}
work();
}
};
I have a pretty good guess that the error may be coming from "const neko = new client();" although im not entirely sure.
I've tried a handful of solutions in attempting to fix the issue such as adding
NODE_TLS_REJECT_UNAUTHORIZED='0'; into my index.js (main file), npm config set strict-ssl=false in my IDE's console, NODE_TLS_REJECT_UNAUTHORIZED='0' node index.js into my IDE's console as well, and set NODE_TLS_REJECT_UNAUTHORIZED='0' in my windows console and none have worked so far. Any solutions?
question from:
https://stackoverflow.com/questions/65650713/how-to-fix-the-self-signed-certificate-in-certificate-chain-error-on-discord-js 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…