Re: External access

First, start testing you machine port is available in your local network run python manage.py runserver 0.0.0.0:8000 In other machine in the same network test it Suppose your django machine has internal ip address 192.168.1.100, then try to access 192.168.1.100:8000 from your web browser in the

Re: External access

When you reply to a message please include the previous emails of that thread. People who read this list on a mail client might have deleted them and they are probably not going to look them up elsewhere in order to remember what the problem was. So, how are you running the Django development

Re: External access

Here is an update on my situation. Windows firewall - I setup in and outbound rules for port 8000 (UDP and TCP) Router - I set up port forwarding for port 8000 (UDP and TCP) Using example code in the socket module documentation I ram socket_client and socket_server on my local machine with the

Re: External access

I don't totally understand how it works under the hood, but using the answer Michal Petrucha provided earlier has worked for me in this situation independent of the OS and any router settings. Run the server using: python manage.py runserver *0.0.0.0:8000 * You'll be able to

Re: External access

> Connecting To 24.211.133.163...Could not open connection to the host, on port > 23: Connect failed. You forgot to specify port, command should be 'telnet 24.211.133.163 8000' (if you're running Django on different port, change 8000 to your port). > How would I do that? I believe it was

Re: External access

On 11/7/2016 1:23 PM, GMail wrote: Wow... Indeed, in Windows telnet is disabled by default. Here's how you can enable it (first link on Google): https://www.rootusers.com/how-to-enable-the-telnet-client-in-windows-10/ C:\Users\bgailer>telnet 24.211.133.163 Connecting To 24.211.133.163...Could

Re: External access

Wow... Indeed, in Windows telnet is disabled by default. Here's how you can enable it (first link on Google): https://www.rootusers.com/how-to-enable-the-telnet-client-in-windows-10/ I believe the problem is (how

Re: External access

On 11/7/2016 8:58 AM, Andreas Kuhne wrote: Do you have "ALLOWED_HOSTS" correclty configured in django settings? Thanks - was not aware of that. Now it looks like: ALLOWED_HOSTS = ['209.216.2.211', '209.216.15.70', '24.211.133.163'] The last one is my external ip Adding the ip addresses did not

Re: External access

On Mon, Nov 7, 2016 at 1:15 PM, bob gailer wrote: > On 11/7/2016 8:50 AM, Larry Martell wrote: >> >> On Mon, Nov 7, 2016 at 8:48 AM, bob gailer wrote: >>> >>> I am running a the django server, listening at port 8000. I can access >>> the >>> server using

Re: External access

On 11/7/2016 8:51 AM, GMail wrote: Hi! Seems like port forwarding doesn't work correctly. Do you have any other ports forwarded (like ssh or ftp)? If so, do they work as expected? What is this command's output: telnet 8000 Sorry but I'm running Windows 10 which does not recognize "telnet"

Re: External access

On 11/7/2016 8:50 AM, Larry Martell wrote: On Mon, Nov 7, 2016 at 8:48 AM, bob gailer wrote: I am running a the django server, listening at port 8000. I can access the server using localhost. When I try using my external ip address I get "The server at 24.211.133.163 is

Re: External access

On Mon, Nov 07, 2016 at 08:48:25AM -0500, bob gailer wrote: > I am running a the django server, listening at port 8000. I can access the > server using localhost. When I try using my external ip address I get "The > server at 24.211.133.163 is taking too long to respond." I have port 8000 >

Re: External access

Do you have "ALLOWED_HOSTS" correclty configured in django settings? Regards, Andréas 2016-11-07 14:48 GMT+01:00 bob gailer : > I am running a the django server, listening at port 8000. I can access the > server using localhost. When I try using my external ip address I get

Re: External access

Hi! Seems like port forwarding doesn't work correctly. Do you have any other ports forwarded (like ssh or ftp)? If so, do they work as expected? What is this command's output: telnet 8000 > On 7 Nov 2016, at 16:48, bob gailer wrote: > > I am running a the django server,

Re: External access

On Mon, Nov 7, 2016 at 8:48 AM, bob gailer wrote: > I am running a the django server, listening at port 8000. I can access the > server using localhost. When I try using my external ip address I get "The > server at 24.211.133.163 is taking too long to respond." I have port

External access

I am running a the django server, listening at port 8000. I can access the server using localhost. When I try using my external ip address I get "The server at 24.211.133.163 is taking too long to respond." I have port 8000 forwarded to my server computer in my router. What more do I need to

Re: Django external access [Windows]

Good news. Weird thing happened. I am okay with the access. It seems like even with the DNS service such as no-ip.org still requires the users to access via abc.no-ip.org:8000 instead of abc.no- ip.org. But I thought I had tried abc.no-ip.org:8000 already yesterday. Thank you, Sam. On Jun 6,

Re: Django external access [Windows]

Does it work from another machine on the same local network? This is definitely possible though; I've done it before. On 6 June 2010 14:35, John Yeukhon Wong wrote: > I just disabled the FW, but no luck with any trials. > > Yeah. Security isn't my concern because only a

Re: Django external access [Windows]

I just disabled the FW, but no luck with any trials. Yeah. Security isn't my concern because only a few people (including myself) will learn about this project. They will only see the interfaces at certain stages when I give out notifications. I am sure in Linux there isn't any problem with

Re: Django external access [Windows]

Oops. Seems like you've tried that already. Have you checked your Windows firewall settings? On 6 June 2010 13:53, Sam Lai wrote: > By default, the Django development server does not allow hosts to > connect unless it is localhost (127.0.0.1) or a local IP > (192.168.1.101

Re: Django external access [Windows]

By default, the Django development server does not allow hosts to connect unless it is localhost (127.0.0.1) or a local IP (192.168.1.101 in your case). Doing this is a *bad idea*, as indicated by the docs - http://docs.djangoproject.com/en/1.2/ref/django-admin/#djadmin-runserver If you really

Django external access [Windows]

For my home purpose, currently I am running Windows XP. I have everything ready. Django, Python are all good. If I let the runserver (I am using the django-development server) to be 127.0.0.1:8000 or 192.168.1.101:8000 they all worked. Let say abc.no-ip.org is a FREE DNS service I use to access