Hello, I'm very sorry for the delay in letting you both know how it worked out for me.
I first tried Cook's method and signed up for the NO-IP service. But for some reason, I could not reach my local server from my phone's browser using the URL that I created there. (But I could access the URL from the computer and it showed the app I was working on.) So, I kept looking for more solutions like it, especially since I want to be able to connect to my computer even when I am on a different network (library, cafe, etc.). I came across LocalTunnel and ngrok (with which the former was being integrated and merged with). But it didn't work out for me. Maybe it's made for a different platform (I work on Windows.) At this point, using additional info I had gathered from the web, I went into my Firewall settings and setup a new rule to open up port 80 for TCP. I then tried the NO-IP service again, but it didn't work. Again, I kept looking... And Portmap and PageKite came into view. And, since PageKite.net's solution was a single Python script that I had to run on my computer and then try to access my local server from the URL that I set up (e.g. example.pagekite.me), I gave it a try. I then executed "manage.py runserver 0.0.0.0:80" on the command line (in my Django project's directory) It worked when I accessed the local server from both the web and my phone. "Ah," I thought, "the world is right again!" :) Now, I am back to developing and testing both versions (mobile and web) of my site simultaneously. Thank you both for the help and resources pointed out. (And my apologies for the long silence.) I wish you both all the best. :) Sincerely, Muhammad On Dec 9, 2013 2:28 PM, "Timothy W. Cook" <t...@mlhim.org> wrote: > Tim Chase's answer works well for a now and then test. But many static > IPs change every 24 hours or so. Plus you will probably want to do this > many more times in the future as well as ask others to test it on various > devices. . > > I suggest setting up a URL using no-ip.org or similar service. > No-ip.org is free at this level and works great, at least on Ubuntu and > CentOS. I haven't tried other OS's. > > HTH, > Tim > > > > On Mon, Dec 9, 2013 at 5:08 PM, Tim Chase > <django.us...@tim.thechases.com>wrote: > >> On 2013-12-09 10:44, Muhammad Ali wrote: >> > Instructions I found online (such as this one: ) say that I should >> > plug the phone to the computer through a USB and run: manage.py >> > runser 0.0.0.0:8000 and visit this IP address via my phone's >> > browser. But it doesn't work and instead returns an error: >> > >> > "Oops! Google Chrome could not connect to 0.0.0.0:8000" >> >> The "runserver 0.0.0.0:8000" tells Django to listen on all interfaces >> you have. You'd have to determine the IP address of your server >> (well, dev machine). Usually you can get this from the output of >> "ifconfig -a" (or "ipconfig /all" on Win32). It will usually return >> something like 192.168.x.y >> >> Depending on how you're tethered, you want to point your phone to >> that address: >> >> http://192.168.3.14:8000/ >> >> Some tethering forces the phone to appear outside your network, >> preventing it from seeing the private/internal 192.168.x.y >> addresses. This complicates matters, as you'd have to adjust your >> router/NAT to open port 8000 (or port 80 for that matter) and point >> it at your box internally. You'd then have to visit your site via >> your external IP address. So you it might look something like >> >> phone >> | >> v >> internet >> | >> v >> router 123.45.67.89 >> | >> | configure router NAT to listen on 80 >> | and forward internally >> | to 192.168.x.y on port 8000 >> v >> computer 192.168.x.y listening on port 8000 >> >> You can find your external IP address by just googling for it: >> >> https://www.google.com/search?q=my+IP+address >> >> which includes the answer before the other actual search results. >> Once you have that external address, you can use >> >> http://123.45.67.89/ >> >> to access it (note that if you forward 8000-to-8000 instead of >> 80-to-8000, you'd have to specify the port as :8000 in the URL) >> >> -tkc >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/20131209130815.323c8fd8%40bigbox.christie.dr >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > MLHIM VIP Signup: http://goo.gl/22B0U > ============================================ > Timothy Cook, MSc +55 21 94711995 > MLHIM http://www.mlhim.org > Like Us on FB: https://www.facebook.com/mlhim2 > Circle us on G+: http://goo.gl/44EV5 > Google Scholar: http://goo.gl/MMZ1o > LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACmdHUbUYnGKa0PsOGZOvpqaox_PrEoBRNOT9p1D7MRtiwJiGQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
