Invalid RPC remote node identifier #743

New Issue

Closed

opened 2024-03-01 03:22:40 +00:00 by olynch · 1 comment

olynch commented

2024-03-01 03:22:40 +00:00

When I try to access the bucket RPC remotely, with --rpc-host=xxxx@example.org:3901, I get an error

Error: Invalid RPC remote node identifier: xxxx@example.org:3901. Expected format is <full node id>@<IP or hostname>:<port>.

When I try to access the bucket RPC remotely, with --rpc-host=xxxx@example.org:3901, I get an error ```txt Error: Invalid RPC remote node identifier: xxxx@example.org:3901. Expected format is <full node id>@<IP or hostname>:<port>. ```

lx commented

2024-03-01 09:57:54 +00:00

Owner

You should get the complete remote identifier of the destination node using garage node id and use that. It will give you complete instructions on how to connect your nodes together.

You should get the complete remote identifier of the destination node using `garage node id` and use that. It will give you complete instructions on how to connect your nodes together.

lx closed this issue

2024-03-01 09:57:54 +00:00

Sign in to join this conversation.

No Label

S3 Compatibility

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#743

No description provided.