Assigning dedicated IPs to clients
Picking one for a client, changing it, and lending one to somebody else.
A dedicated IP is assigned to a client on the client itself: the Dedicated IP step of the create form, or by editing a stopped client. Each choice shows its latency so you can pick a fast one. Dedicated IPs are part of a plan.
No dedicated IP is a valid choice: the client connects through the platform's shared IPs. Those take a limited number of clients per account, shown on the Shared pool card in the Dedicated IPs section; past it, a start is refused until a client is stopped or given a dedicated IP.
When to give a client one
A dedicated IP gives the client a stable connection that is not shared with other customers. Give one to a client when:
- you want the client to keep the same address from one session to the next;
- you want its traffic isolated from everybody else's.
Always follow the rules of the server you connect to, including any limit it sets on how many connections you may have.
Changing it
The client has to be stopped, because the dedicated IP is one of the fields locked while it runs. The exception is Swap dedicated IP for a dead one, which exists precisely so you can fix a broken client in one click.
To set the dedicated IP of many stopped clients at once, select them on the Clients page and use Dedicated IP. Pick one to use it for all of them, or several to spread them out.
Sharing a dedicated IP
A dedicated IP can be shared with other people, one grant per person, from its drawer on the Clients page. See sharing. They never see the password, and the Geonix API key is not shared with it.
What a grantee can do with it today is test it from their Shared page. Attaching a shared dedicated IP to their own client is described by the Control level but is not offered in the panel: the client's picker only lists the ones you own. See access levels.
Spares
Deleting a client keeps its dedicated IP. It returns to the list, marked not used by any client, ready for the next one.