UNAUTHORIZED — Request was not authorized

The agent requires credentials the request did not carry.

Start free MTConnect → canonical

Diagnosis

When you hit this

An agent behind a reverse proxy enforcing authentication that the client does not supply.
Token or certificate expiry on a secured agent.

Resolution

How to fix it

Check the proxy, not the agent
Most MTConnect agents have no native auth. A 401 usually originates from something in front of it.
Confirm token expiry
Long-lived collectors commonly fail this way weeks after a working deployment.

Normalization

What Forge does about it

This is a configuration or addressing mistake on the wire, upstream of anything Forge sees. Where Forge helps is the step after you fix it: once the point returns data, its vendor tag name maps to a canonical field automatically, so you do not also have to hand-maintain a name table for every point you just re-addressed.