gravitational/teleport · error

proto: wrong wireType = %d for field Name

Error message

proto: wrong wireType = %d for field Name

What it means

Generic protobuf wire-format guard generated by protoc-gen-go in the Unmarshal method for a message with an ARN field (IdentityCenter types in authservice.pb.go). It fires when binary protobuf input is malformed: field 2 (Name) arrives with a wire type other than 2 (length-delimited), meaning the serialized bytes are corrupt, truncated/reframed, or produced by an incompatible schema/version.

Source

Thrown at api/client/proto/authservice.pb.go:60881

					break
				}
			}
			intStringLen := int(stringLen)
			if intStringLen < 0 {
				return ErrInvalidLengthAuthservice
			}
			postIndex := iNdEx + intStringLen
			if postIndex < 0 {
				return ErrInvalidLengthAuthservice
			}
			if postIndex > l {
				return io.ErrUnexpectedEOF
			}
			m.ARN = string(dAtA[iNdEx:postIndex])
			iNdEx = postIndex
		case 2:
			if wireType != 2 {
				return fmt.Errorf("proto: wrong wireType = %d for field Name", wireType)
			}
			var stringLen uint64
			for shift := uint(0); ; shift += 7 {
				if shift >= 64 {
					return ErrIntOverflowAuthservice
				}
				if iNdEx >= l {
					return io.ErrUnexpectedEOF
				}
				b := dAtA[iNdEx]
				iNdEx++
				stringLen |= uint64(b&0x7F) << shift
				if b < 0x80 {
					break
				}
			}
			intStringLen := int(stringLen)
			if intStringLen < 0 {

View on GitHub (pinned to 1283425b60)

Solutions

1. Verify sender and receiver use compatible protobuf definitions/versions of authservice
2. Check for truncated or corrupted payloads and re-send the request

When it happens

Trigger: Thrown at api/client/proto/authservice.pb.go:60881 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of gravitational/teleport@1283425b60 (2026-09-02). Data as JSON: /api/errors/ae37c7b1de946818. Report an issue: GitHub.