I’m having issues making sure that Digital Ocean sends the correct Client IP Address whenever I make a server side request from nextjs to another app.
x-forwarded-for and do-connecting-ip seem to be sending IPs from digital ocean/cloudfare instead of the IP addresses of the client that made the request.
I already debugged this and the server side request is sending the right IP addresses, but digital ocean seems to be switching them when the request is actually sent.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hey Manuel!
That does sound like what usually happens on App Platform, as traffic flows through Cloudflare and DigitalOcean’s infrastructure, headers like x-forwarded-for or do-connecting-ip might not always reflect the original client IP.
Usually, the first IP in the x-forwarded-for header is the actual client’s, but that might vary depending on how requests are being handled or proxied.
If you’re already passing the right IP and it’s getting swapped out later, it could be something internal to how App Platform manages outbound requests. You might want to reach out to the DigitalOcean support directly, they should be able to confirm if there’s any rewriting happening on their end.
Let me know how it goes, this could help others too!
- Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.