<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: RuchiDeo</title>
    <description>The latest articles on DEV Community by RuchiDeo (@ruchideo266).</description>
    <link>https://dev.to/ruchideo266</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3831285%2F374e81bd-b39f-4b04-ab68-ab826232b920.jpeg</url>
      <title>DEV Community: RuchiDeo</title>
      <link>https://dev.to/ruchideo266</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ruchideo266"/>
    <language>en</language>
    <item>
      <title>How to fix a deployed app that works on Wi-Fi but not on a mobile network?</title>
      <dc:creator>RuchiDeo</dc:creator>
      <pubDate>Sat, 04 Apr 2026 17:10:58 +0000</pubDate>
      <link>https://dev.to/ruchideo266/how-to-fix-a-deployed-app-that-works-on-wi-fi-but-not-on-a-mobile-network-1gmd</link>
      <guid>https://dev.to/ruchideo266/how-to-fix-a-deployed-app-that-works-on-wi-fi-but-not-on-a-mobile-network-1gmd</guid>
      <description>&lt;p&gt;&lt;strong&gt;My friend, you’re trying to fix an app deployment that works perfectly on Wi-Fi but fails to load over mobile data. You’ve checked every configuration but have no idea where the leak is. I have the solution to your problem.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The culprit: DNS blocking by your ISP (Internet Service Provider).&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;Before jumping into the fix, keep two things in mind:&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You need a custom domain.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;If you’re using a free hosting service, this issue is incredibly common (especially for us developers in India!).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s the solution?&lt;/strong&gt;&lt;br&gt;
Use Cloudflare.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How does it solve the problem?&lt;/strong&gt;&lt;br&gt;
It’s simple. &lt;strong&gt;Cloudflare adds a proxy layer that acts as a middleman between your domain and where you’ve hosted your frontend and backend.&lt;/strong&gt; Instead of the ISP blocking the hosting provider's "flagged" IP, they only see Cloudflare’s "clean" IP.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Steps:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Point your domain to Cloudflare:&lt;/strong&gt; Change the Nameservers in your original domain registrar (like GoDaddy or Namecheap) to the ones provided by Cloudflare.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Configure your Hosting Platforms:&lt;/strong&gt; Go to the settings of both your frontend and backend providers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Add a Custom Domain:&lt;/strong&gt; Select the "Add Custom Domain" option. The provider will give you specific DNS settings (like CNAME or A records).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update Cloudflare Records:&lt;/strong&gt; Go to the DNS tab in your Cloudflare dashboard. Click Add Record and enter the credentials provided by your host.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Submit and Wait:&lt;/strong&gt; Once you save, you’re done! Give it some time for the changes to reflect globally (DNS propagation).&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If you need more details on this topic and hear my struggle story, visit RantDoc:&lt;/strong&gt; &lt;a href="https://rantdoc.peropeko.com/rant/articles/33" rel="noopener noreferrer"&gt;How to Fix DNS Blocks and “ISP Only” Access with Cloudflare&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's it for now.&lt;/p&gt;

&lt;p&gt;See ya!!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>beginners</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
