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, 1
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 few people (including
> m
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 overri
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 in your case).
>
> Doi
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 do
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
6 matches
Mail list logo
