remotes

List of entries specifiying servers where the leaf node client connection can be made.

Values

Type	Description	Choices
`[ object ]`	An object with a set of explicit properties that can be set.	-

Name	Description	Type	Default
`url`	URL or list of URLs of a remote server accepting leaf node connections. If username/password or token authentication is required on the remote, this should be encoded in the URL itself, e.g. `nats-leaf://username:password@localhost:7422`. Note, the URL scheme should be `nats-leaf` or `ws`.	`(multiple)`	-
`no_randomize`	If true and more than one URL is specified, the first one in the list will be used. If the client disconnects from the server, then the next URL will be used in order.	`boolean`	-
`account`	Account name or public NKey identifying the local account to bind to this remote server. Any traffic locally on this account will be forwarded to the remote server.	`string`	-
`credentials`	Path to a credentials file. This is application when decentralized auth is used on the remote.	`string`	-
`tls`	TLS configuration for connecting/authenticating with the remote if mutual TLS is required.	`object`	-
`hub`		`boolean`	-
`deny_imports`		`(multiple)`	-
`deny_exports`		`(multiple)`	-
`ws_compression`	If true, and connecting with the WebSocket protocol, the connection will indicate to the remote that it wishes compression to be used.	`boolean`	`false`
`ws_no_masking`	If true and connecting with the WebSocket protocol, the connection will indicate to the remote that it wishes not to mask outbound WebSocket frames.	`boolean`	`false`
`jetstream_cluster_migrate`		`boolean`	`true`