FCPv2 ProtocolError

ProtocolError is sent by the node whenever an error in the FCP communication occurs. When sent by the client, this message causes the node to log an error message.

Example

ProtocolError
Identifier=request-identifier
Code=16
CodeDescription=Not supported
ExtraDescription=
Fatal=true
Global=false
EndMessage

Fields

Field	Description
Identifier	The identifier of the request that caused the error.
Code	The numerical code of the error.
CodeDescription	A human-readable description of the error.
ExtraDescription	Additional information about the error.
Fatal	true if the error is fatal for the request, false otherwise.
Global	true if the request was on the global queue, false otherwise.

Error Codes

The following error codes are currently in use:

Code	Description
1	ClientHello must be first message
2	No late ClientHello’s accepted
3	Unknown message parsing error
4	Error parsing freenet URI
5	Missing field
6	Error parsing a numeric field
7	Don’t know what to do with message
8	Invalid field value
9	File not found, not a file or not readable
10	Disk target exists, refusing to overwrite for security reasons
11	Is not used anymore.
12	Could not create file
13	Could not write file
14	Could not rename file
15	No such identifier
16	Not supported
17	Internal error
18	Shutting down
19	No such nodeIdentifier
20	Error parsing URL
21	Reference could not be parsed
22	File could not be read
23	Filepath is not a file
24	Access denied
25	Direct Disk Access operation denied: did you send a FileHash field ? Did you use TestDDA?
26	Could not read file
27	Reference signature failed to verify
28	Node cannot peer with itself
29	Node already has a peer with that ref
30	Opennet is currently disabled in the node’s configuration
31	Operation only available on a darknet peer
32	No such plugin
33	Persistence disabled (e.g. encrypted queue waiting for password?)
34	Too many files in a single folder on a freesite insert
35	Bad MIME type
36	Not supported for that return type
37	Disk I/O error
38	Plugins disabled