A VPN server is a remote node that a client on a phone, computer or router connects to. It receives secure traffic and sends it on to a website, app or private network. That’s why a website usually sees the server’s IP rather than the user’s network. Let’s look at how this part of a VPN works in practice and how to choose the right node.
What a VPN server is, in simple terms
Think of it as a secure transfer point for internet traffic. The device first establishes a tunnel to it, and then the server reaches out to the needed address. It authenticates the client, applies routing rules and forwards packets.
A regular web server serves pages, while a VPN server terminates the tunnel and routes traffic. The VPN protects the leg up to the server; with HTTPS, the content also stays encrypted on the way from the app to the website.
How a VPN server differs from a VPN service and app
A VPN combines several elements. The server is part of that infrastructure, not an alternative to a VPN.
VPN client
This is an app or system component on the device. The client receives the connection parameters, authenticates and routes either all traffic or specific routes into the tunnel.
VPN server
The remote side of the connection listens on the configured address and port, checks keys, certificates or credentials, negotiates a secure channel and routes the allowed traffic.
VPN service
A ready-made offering bundles servers, apps or configurations, account management and support. The provider defines the locations, protocols, number of devices and how technical data is handled.
At MeduzaVPN this infrastructure is delivered as a ready-made service: a personal VPS, a separate IP, automatic server setup, apps and configurations for compatible clients.
What a VPN server is for
A consumer VPN routes internet traffic through the server, while a corporate one provides access to closed resources. With split tunneling, part of the addresses go through the tunnel and part go directly.
Protecting transmitted data
The client and server create a secure channel according to the rules of the VPN protocol. This hides the tunnel’s contents from the local Wi-Fi owner and the access provider. They can still see that a connection exists, the server’s address, the time and roughly how much data was exchanged.
Changing the visible IP address
The request goes out onto the internet with the VPN server’s IP, so a website usually does not get the user’s original address. Exceptions are possible with split routing or leaks. The new IP also does not hide an account, cookies or a browser fingerprint.
Secure remote access
A VPN server can act as a gateway into a work, corporate or home network. After authentication, the user gets access to the allowed internal resources. A gateway like this needs to be kept updated, restricted by permissions and protected with strong authentication.
Connecting users and devices
The server accepts connections from computers, smartphones, tablets and compatible routers. It is best to issue a separate profile or key for each device. The number of sessions is limited by settings, resources and the service’s terms.
How a VPN server works
- The client receives the address, port, protocol and authentication parameters.
- The two sides authenticate each other and negotiate session keys.
- The client wraps the selected packets and secures them.
- The server strips the VPN wrapper and routes the request.
- The response is placed back in the tunnel and returned to the client.
- The client unwraps the data for the app.
The server removes the VPN tunnel’s protection in order to route packets. The content of an HTTPS request still stays encrypted all the way to the website.
Types of VPN servers
Servers differ in where they are hosted, who uses them and their resources. For example, a private VPN server can run as a virtual machine.
Physical and virtual servers
A physical server is a separate piece of hardware. A VPS is an isolated virtual environment with allocated resources. The format itself does not determine quality — resources, the channel, the route and maintenance matter more.
Shared VPN servers
Many clients connect to a shared server. They split computing resources, the channel and often the exit IP. Load and the address’s reputation can depend on other users.
Private and dedicated VPN servers
A private server is provided to a single owner, family or team. The tunnel scheme is the same, but there are no other clients on the instance, and the IP can be its own. The host and the data center’s backbone can still be shared. Terms and available locations are published on the servers page.
Every MeduzaVPN server is dedicated to one customer and their devices: no other users share the instance or the exit IP with them. That makes load and the address’s reputation more predictable compared with shared VPN pools.
| Criterion | Shared | Private |
|---|---|---|
| IP address | Usually one address is used by many clients | Often a separate IP for the owner or group |
| Load | Depends on the number of active users and load balancing | No load from other users on the instance |
| Stability | Can vary at peak hours and because of the shared IP | Usually more predictable given sufficient resources |
| Resources | Split between sessions | Assigned to the instance or group under the plan |
What data a VPN server can see
Technically, the server side may have access to:
- the client’s original IP;
- session time, protocol and traffic volume;
- destination addresses and ports;
- DNS requests, if they are handled by a server-side resolver;
- unencrypted content, such as HTTP.
Being able to access this data does not mean it is necessarily logged. Storage is set by the configuration and the service’s rules. With HTTPS, the server does not get the plaintext password or page text, but it can see the connection’s metadata. A VPN shifts trust to the operator rather than removing the need for it. So check the details on security and data handling.
MeduzaVPN’s apps do not collect or transmit user activity, and the protocols run in isolated containers with no internal logs on the personal VPS.
How to choose a VPN server and what determines speed
Speed is limited by the narrowest link: the original connection, the routes, the server’s resources and channel, or the website itself. Encryption also adds overhead.
Server location
A longer path usually increases latency, so for calls and games start with a nearby location. The geographically closest node is not always the closest one on the network: compare a few options.
Server load
When active clients compete for the processor and channel, latency and packet loss can rise and speed can drop. A private instance rules out load from other VPN clients on it, but not the data center’s overall load.
Bandwidth and resources
Channel width sets an upper limit but does not guarantee it to every device. The processor, the plan, peering and packet loss also play a role. A single test only describes one specific route at one moment.
Server type and VPN protocol
The protocol determines the encryption, transport and how the connection behaves under packet loss or when switching networks. An incorrect MTU can slow things down. If your connection is unstable, compare WireGuard and OpenVPN in the same location — there is no single fastest option that works for everyone.
What data you need to connect to a VPN server
For manual setup you need the address, port, protocol and authentication parameters: a password, certificate or keys. A configuration file and QR code can contain secrets, so never publish them. Use the official account dashboard or the help center.
MeduzaVPN automatically sets up the server and connection: apps are available for Windows, Android, iOS and macOS, while ready-made configurations and QR codes cover Linux, routers and compatible clients.
VPN server address
This is the node’s public IPv4, IPv6 or domain name. DNS resolves the domain into an IP. A mistake in the address leads to a timeout or a connection to the wrong server.
VPN server port
A port is a numeric identifier for the service. The server has to listen on it, the client has to use the right protocol, and the firewall has to let it through. The port itself does not encrypt data.
VPN protocol
The protocol sets the rules for authentication, key exchange and packet protection. The client and server have to support a compatible version. Private keys and the full QR code count as secrets.
How to check that a VPN server is working
First take a measurement without the VPN, then repeat it after connecting. IP, DNS, speed and stability are different metrics, so one test is not enough.
Checking the IP address
- Note your external IPv4 and IPv6 before connecting.
- Connect and repeat the check in a private window.
- Make sure the IP has changed and belongs to the chosen server.
- Check both address families: your original IPv6 can bypass the tunnel.
Geolocation databases make mistakes, so the address matters more than the exact city. An unchanged IP can be the result of split tunneling or a proxy.
Checking DNS requests for leaks
After connecting, run a DNS leak test. With a full tunnel, seeing your home provider among the resolvers is a reason to check your settings. DNS over HTTPS and split DNS can intentionally produce a different result, so compare it against your configuration.
Checking speed and latency
Compare download, upload and ping with and without the VPN, on the same device and test node. Take several measurements and look at the median. For calls and games, jitter and packet loss matter too. If you run into problems, change the location and protocol one at a time.
Checking stability
Leave the connection running for 15–30 minutes and use your usual apps. Note any drops, ping spikes and failures when switching networks. After reconnecting, check the IP and DNS again. Never send support your private keys or the full configuration file.
Conclusion
A VPN server accepts the secure tunnel, authenticates the client and routes requests to the internet or a private network. The result depends on location, load, resources, route and protocol. Check where a configuration comes from, and after connecting, check the IP, DNS, speed and stability.
To avoid deploying and maintaining a server yourself, you can launch a personal VPS through MeduzaVPN and immediately get a separate IP, your chosen location and ready-made connection methods.
FAQ
How does a VPN server differ from a VPN?
A VPN is a technology for a secure connection, and a VPN server is one of its nodes. You also need a client, a protocol and access parameters for it to work. A VPN service bundles these components into a ready-made offering.
Can one VPN server be used on several devices?
Yes, if the server’s resources and the service’s terms allow it. It’s better to create a separate profile or key for each device. Simultaneous connections share the available bandwidth.
Do you have to configure a VPN server yourself?
Not necessarily: a managed VPN service can prepare the server and configuration automatically. With a self-hosted deployment, the owner is responsible for installation, updates, the firewall and the keys.
Why does one VPN server work faster than another?
Speed is affected by distance and route, load, channel width, processor resources, packet loss and the protocol. The result also depends on your internet provider and the time of day.
Does the IP address change when you switch VPN servers?
Usually, yes: a different exit node has a different public IP. The exception is a shared gateway serving several servers. After switching, it’s worth checking both IPv4 and IPv6.
Can you stay connected to the same VPN server all the time?
Yes, if its IP, location and route suit your needs. In case of maintenance or an outage, it helps to have a backup server or protocol.