Accessing Django through ssh tunneling and error to get status

[Dikus Extrange]

Hi everyone. I'm accessing to a Django application through a ssh tunnel with putty as client. I run the server with ./manage.py run server 127.0.0.1:8000 and it starts right but launching an infinite and annoying message:

Not found: /http:/127.0.0.1:8000/status

[12/Jul/2018 10:02:59] "GET http://127.0.0.1:8000/status?plain&encode=b64&set_os_username=RE1Dxxxxx&osid=1 HTTP/1.1" 404 1768

...

...

Could anyone tell me if it's a bug of Django, a missconfiguration or what?

Running the server without ssh tunneling is OK. I had to add localhost.localdomain and 127.0.0.1 to allowed hosts in settings.py.

Django version 2.0.6.

Thank you in advance. 

Dikus

[Jason]

you should use 0.0.0.0 for the ip address rather than 127.0.0.1

[Dikus Extrange]

Hi Jason. Thank you for your reply. I tried with your suggestion. 

Django complained about putting then name of my laptop and its domain in allowed hosts (I had to put 'localhost' and '127.0.0.1' before). So I put it in settings.py and the. Result is the same with the same message. 

[Robert Edward]

Hey, uhm I faced a similar problem lately. Try this in the Settings.py file, 

Inside the brackets insert an asterisk ✳ 

It should look something like this 

Allowed host = [ *];

Then try again. 

--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a42794fb-e9d8-4aa5-8e22-3180e4ef53eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dikus Extrange]

Hi Robert. Thank you for your piece of advice. I tried writting

ALLOWED HOSTS = ['*',]

And after running the server, it throws the same message:

Not Found: /http:/127.0.0.1:8000/status
Etc,etc...

I wonder why the protocol has only a slash (http:/ rather http://). Could it be a wrong message?

[Melvyn Sopacua]

On maandag 16 juli 2018 08:56:06 CEST Dikus Extrange wrote:

 

> Not Found: /http:/127.0.0.1:8000/status

> Etc,etc...

>

>

> I wonder why the protocol has only a slash (http:/ rather http://). Could it

> be a wrong message?

 

This looks like a wrongly configured status monitor of some sorts, like for example using nginx health checks. But there are more implementations, so don't focus on the nginx part.

 

Probably the quickest way to identify the culprit is to use sysadmin utilities like sockstat, netstat and similar.

 

--

Melvyn Sopacua