Vercel treats Oracle server IP as local IP - Connection failing #191128
-
🏷️ Discussion TypeBug BodyHi everyone, I'm facing an issue while connecting my Vercel deployment to an Oracle database server. The problem is that Vercel seems to be treating the Oracle server's IP address as a local/internal IP. Because of this, the request never actually leaves the Vercel environment to reach my backend database. Has anyone faced this routing issue before? Is there a way to force Vercel to treat this specific IP as an external address or any configuration in vercel.json that can fix this? Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Hi @naqvi110k, Instead of using the direct IP address of your Oracle server, you should try using DuckDNS. Create a free domain on DuckDNS and point it to your server's IP. Then, use that DuckDNS hostname in your Vercel environment variables. This way, Vercel will treat it as a regular external domain and route the connection properly through the public internet. Hope this helps you fix the routing issue! |
Beta Was this translation helpful? Give feedback.
Hi @naqvi110k,
Instead of using the direct IP address of your Oracle server, you should try using DuckDNS.
Create a free domain on DuckDNS and point it to your server's IP. Then, use that DuckDNS hostname in your Vercel environment variables. This way, Vercel will treat it as a regular external domain and route the connection properly through the public internet.
Hope this helps you fix the routing issue!