Overview

If you've configured ChangeMyIP but your IP address isn't changing, the issue is usually a configuration error, authentication problem, or DNS leak. This guide walks you through verifying that your traffic is actually routed through ChangeMyIP proxies for HTTP/HTTPS, SOCKS5, and WireGuard, and provides troubleshooting steps for common failure points.

ChangeMyIP offers datacenter and residential proxies with HTTP, SOCKS5, Shadowsocks, Trojan, DNS, and WireGuard protocols across 40+ countries. This tutorial focuses on the three most common protocols for IP rotation and assumes you have already purchased a plan and have your proxy credentials.

Prerequisites

A ChangeMyIP account with an active flat monthly plan.
Proxy credentials (username, password, host, port) for your chosen protocol.
Command-line tools: curl (for HTTP/SOCKS5 tests) and wg (for WireGuard).
Administrative access to your device.

Steps

Verify your current IP without a proxy

Before testing any proxy, confirm your real IP. Use a reliable IP echo service:
```
curl -s https://api.ipify.org
```
Note the output. This is the IP you want to change.
Test ChangeMyIP HTTP/HTTPS proxy

Configure curl to use your HTTP proxy. Replace the placeholders with your credentials:
```
curl -x http://<username>:<password>@<proxy-host>:<port> -s https://api.ipify.org
```
If the output is different from your real IP, the HTTP proxy is working. If not, proceed to troubleshooting.
Test ChangeMyIP SOCKS5 proxy

SOCKS5 works at a lower level and supports UDP. Test it with curl:
```
curl --socks5 <username>:<password>@<proxy-host>:<port> -s https://api.ipify.org
```
Again, compare the result to your real IP. If it matches your real IP, the proxy is not being used.
Test ChangeMyIP WireGuard

If you have a WireGuard configuration file from ChangeMyIP, import it and bring up the tunnel:
```
sudo wg-quick up changemyip
```
Verify the handshake:
```
sudo wg show
```
Then check your IP:
```
curl -s https://api.ipify.org
```
The IP should reflect the WireGuard endpoint's location.
Check for DNS leaks

Even if your IP changes, DNS requests may leak your real location. Use a DNS leak test site or run:
```
curl -s https://1.1.1.1/cdn-cgi/trace
```
Look for the ip= line. If it shows your real IP, your DNS is not routed through the proxy. For SOCKS5, use --socks5-hostname to force remote DNS resolution:
```
curl --socks5-hostname <username>:<password>@<proxy-host>:<port> -s https://api.ipify.org
```
Verify residential proxy rotation

If you are using rotating residential proxies, each request may use a different IP. Test with multiple requests:
```
for i in {1..5}; do curl -x http://<username>:<password>@<proxy-host>:<port> -s https://api.ipify.org; echo; done
```
You should see different IPs. If not, your plan may be configured for sticky sessions (same IP for a duration). Check your ChangeMyIP dashboard for rotation settings.

Troubleshooting

Authentication errors: Ensure your username and password are correct. Some proxies require IP whitelisting instead of username/password. Check your ChangeMyIP dashboard for the authentication method.
Connection timeouts: Verify the proxy host and port. Firewalls may block non-standard ports. Try a different port if available.
IP not changing with HTTP proxy: Some applications ignore system proxy settings. Use curl -x explicitly or configure the app's proxy settings.
SOCKS5 returns real IP: You may be using --socks5 instead of --socks5-hostname, which resolves DNS locally. Use the latter.
WireGuard handshake fails: Check that your private key and endpoint are correct. Ensure UDP port is not blocked.
Sticky sessions: If you see the same IP repeatedly, your residential proxy may be using sticky sessions. Rotate the session ID or wait for the sticky duration to expire.

Summary

Verifying that ChangeMyIP actually changes your IP involves testing each protocol separately, checking for DNS leaks, and understanding rotation behavior. By following the steps above, you can isolate whether the issue is in your configuration, authentication, or the proxy service itself. If problems persist, consult ChangeMyIP's documentation or support, and consider testing with a different protocol (e.g., SOCKS5 vs HTTP) to narrow down the cause.