#The user aborted a request. At Client.login. — Page 1

At some point after Dec 27, 1:30 PM (PST), my bot stopped running. I started it up manually (after making sure everything was up to date just in case it was an outdated node module issue), and this is the output:

[nodemon] 2.0.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node index.js`
Started notification cron job.
/usr/share/aocbot/node_modules/discord.js/src/rest/RequestHandler.js:201
        throw new HTTPError(error.message, error.constructor.name, error.status, request);
              ^

HTTPError [AbortError]: The user aborted a request.
    at RequestHandler.execute (/usr/share/aocbot/node_modules/discord.js/src/rest/RequestHandler.js:201:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async RequestHandler.push (/usr/share/aocbot/node_modules/discord.js/src/rest/RequestHandler.js:51:14)
    at async WebSocketManager.connect (/usr/share/aocbot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:134:9)
    at async Client.login (/usr/share/aocbot/node_modules/discord.js/src/client/Client.js:254:7) {
  code: 500,
  method: 'get',
  path: '/gateway/bot',
  requestData: { json: undefined, files: [] }
}

Node.js v18.12.1

It appears to be having an issue logging in but I can't imagine why. Nothing's changed since then that I'm aware of, though I'm not sure how I'd check for shenanigans.

I appear to still only be using discord.js 13.3.1 even though I told it to update. Eventually I figured out how to update it to 13.12, but nothing has changed.