JobEngine AutoCAD Plugin

Sign-in problems

Browser sign-in, staying signed in, and authorization errors.

How sign-in works

  • Sign in: click Sign In on the JobEngine ribbon , or just run LOAD_DT — it starts sign-in automatically if you're not signed in. Your default web browser opens to the JobEngine sign-in page; after you sign in there, the browser shows a success page and you can return to AutoCAD. AutoCAD is intentionally unresponsive while the browser sign-in is open — that's normal; it resumes as soon as sign-in completes.
  • Stay signed in: the plugin stores an encrypted token on your machine and refreshes it automatically. You should rarely need to sign in again.
  • Sign out: run SIGN_OUT_DT. Use it if you're switching accounts or handing the machine to someone else.

Sign-in browser never opens, or shows "127.0.0.1 refused to connect"

Symptom: You run LOAD_DT (or click Sign In) and either no browser window appears, or the browser opens, you sign in successfully, and the final redirect page shows "127.0.0.1 refused to connect" — AutoCAD never finishes signing you in.

Cause: Either you're on an old plugin version with known sign-in bugs (fixed in v0.4.6 and later), or security software on your machine is interfering with the local browser-to-AutoCAD handoff (the sign-in result is delivered over a local-only connection on your own machine).

Fix:

  1. Update to the latest plugin version first — several early versions had exactly this symptom, and updating fixes them all.
  2. Make sure you have a default web browser set in Windows (Settings → Apps → Default apps).
  3. Try again — a transient hiccup during the handoff is recovered by simply re-running LOAD_DT.
  4. If it persists, suspect endpoint-security tools that tunnel all traffic (certain CrowdStrike/Zscaler configurations) — ask IT whether local loopback (127.0.0.1) traffic is being intercepted, and contact support with your log files.

Signed in, but everything starts failing with authorization errors after about an hour

Symptom: Sign-in worked, LOAD_DT/chat worked for a while, then API calls or chat start failing with authorization (401) errors and never recover on their own.

Cause: Your stored sign-in token is from before a server-side change and lacks the long-lived refresh credential, so it expires after roughly an hour.

Fix:

  1. Run LOAD_DT once — it will take you through the browser sign-in again and store a fresh token that auto-refreshes from then on.
  2. If it recurs every session even after a fresh sign-in, update the plugin and contact support with your logs.

Install

AI assistant