NVB Backend Error Codes
These error codes originate from the NVIDIA Backend services and appear in GFN client logs in 0x00000XXX format. They map closely to HTTP status codes.
Error Codes
| Error Code | Decimal | HTTP Equivalent | Name | Description |
|---|---|---|---|---|
0x0000001f5 | 501 | 501 Not Implemented | NVB_R_SERVER_ERROR | Generic server error |
0x0000001f6 | 502 | 502 Bad Gateway | NVB_R_SERVER_OUT_OF_SERVICE | Server/rig out of service |
0x0000001f8 | 504 | 504 Gateway Timeout | NVB_R_SERVER_TIMEOUT | Server didn't respond in time |
0x000000198 | 408 | 408 Request Timeout | NVB_R_REQUEST_TIMEOUT | Client request timed out |
0x0000001ad | 429 | 429 Too Many Requests | NVB_R_RATE_LIMITED | Rate limit exceeded |
Detailed Comparison
| Property | 0x0000001f5 (501) | 0x0000001f6 (502) |
|---|---|---|
| Hex | 0x0000001f5 | 0x0000001f6 |
| Decimal | 501 | 502 |
| GFN Name | NVB_R_SERVER_ERROR | NVB_R_SERVER_OUT_OF_SERVICE |
| Meaning | Generic internal server error | Streaming rig unavailable |
| Retryable | Yes (with backoff) | Yes (with backoff) |
| Common Causes | Server crash, unhandled exception, resource exhaustion | Rig maintenance, rig crash/reboot, capacity shortage |
Client Retry Logic
js
// GFN retries automatically on these errors:
if ([429, 502, 503, 504].includes(statusCode)) {
// Retry with exponential backoff
}
// Specific handling:
501 == status || 502 == status || 408 == status
? retryWithBackoff()
: failImmediately();