Skip to content

routed_ipv6_next_hop_missing

Routed IPv6 conflict. HTTP status 409.

The VPS in vpsId has no IPv6 address on its primary public interface. A routed subnet needs that address as its next hop.

What to do

Add an IPv6 address to the VPS with POST /api/v2/vps/{id}/network (action assign_ip). Then send the create_route request again.

What the message says

  • Enable IPv6 on this VPS before routing a subnet to it.

Example

Response 409
{
"type": "https://developer.hostup.se/errors/routed_ipv6_next_hop_missing",
"title": "Routed IPv6 conflict",
"status": 409,
"detail": "Enable IPv6 on this VPS before routing a subnet to it.",
"code": "routed_ipv6_next_hop_missing",
"requestId": "req_01hxa3b4c5d6e7f8g9h0j1k2m3"
}

Branch on code, not on title or detail. When you contact support about it, include the requestId. More in Errors and retries.

Endpoints that return it