Skip to main content
Errors generated by Massive use status codes in the 452–454 and 470–477 ranges and always include an X-Massive-Reason response header. Any other status code — 403, 404, 500, 502, 503, and so on — comes from the target site and is passed through unchanged. Here are the main error codes and their solutions:
  1. Authentication Error (407):
    • Meaning: The provided credentials are invalid
    • Fix: Verify the username and password format
  2. Bad Request (400):
    • Meaning: The request is malformed
    • Fix: Check routing parameters and request syntax
  3. Disallowed Content (452):
    • Meaning: The request violates Massive’s content policy
    • Fix: Check for restricted protocols or blocked destinations
  4. Port Forbidden (453):
    • Meaning: The requested port is not available on the account
    • Fix: Use port 80 or 443, or request additional ports via support
  5. Target Unresolvable (454):
    • Meaning: The target hostname could not be resolved
    • Fix: Verify that the hostname is correct and publicly resolvable
  6. Capacity and Routing Errors (470–477):
    • 470 (No Nodes Available): No nodes are currently available; retry after a short delay
    • 471 (No Route Match): The geotargeting is too restrictive; relax the constraints
    • 472 (Node Tunnel Failed): A tunnel to a proxy node failed; usually temporary, so retry
    • 473 (Upstream Unavailable): A Massive server was unreachable; usually temporary, so retry
    • 474 (Proxy Internal Error): Retry, and contact support if the error persists
    • 475 (Sticky Node Gone): The session’s node went offline; start a new session
    • 476 (Target Connect Timeout): Connections to the target timed out; increase the connect timeout or check the target
    • 477 (Sticky Node At Capacity): The session’s node is temporarily busy; retry with the same session ID shortly
See Error Types for the full reference, including SOCKS5 reply codes.