Localhost redirects to 127.0.0.1 after updating #776

Closed
Begall opened this Issue Aug 12, 2012 · 14 comments

Comments

Projects
None yet
3 participants
Contributor

Begall commented Aug 12, 2012

Just updated to the latest master from a different machine on the network, but when it comes to reloading the home page, it attempts:

http://127.0.0.1:8181/home

Instead of:

http:192.168.1.etc...

Thought it had crashed till I looked at the address bar!

Owner

rembo10 commented Aug 12, 2012

This might be a new behavior from cherrypy (the web server). What do you
have set as your http_host?
On Aug 12, 2012 6:41 PM, "Begall" notifications@github.com wrote:

Just updated to the latest master from a different machine on the network,
but when it comes to reloading the home page, it attempts:

http://127.0.0.1:8181/home

Instead of:

http:192.168.1.etc...

Thought it had crashed till I looked at the address bar!


Reply to this email directly or view it on GitHubhttps://github.com/rembo10/headphones/issues/776.

Owner

rembo10 commented Aug 12, 2012

Its happening on my end too... localhost:8181 redirects to 127.0.0.1:8181.
I just switched to chromium so i thougt it was a browser thing and didnt
really pay much attention to when it started. Oh well - will get a fix up
soon
On Aug 12, 2012 6:41 PM, "Begall" notifications@github.com wrote:

Just updated to the latest master from a different machine on the network,
but when it comes to reloading the home page, it attempts:

http://127.0.0.1:8181/home

Instead of:

http:192.168.1.etc...

Thought it had crashed till I looked at the address bar!


Reply to this email directly or view it on GitHubhttps://github.com/rembo10/headphones/issues/776.

Owner

rembo10 commented Aug 12, 2012

Can you change the title of the thread to "Localhost redirects to
127.0.0.1" or something so people can find this easier if theyre having the
same problem?

Contributor

Begall commented Aug 12, 2012

Done, thanks :)

Contributor

Begall commented Aug 12, 2012

Also, my HTTP host is set to 0.0.0.0, so I guess that's affected too.

Owner

rembo10 commented Aug 12, 2012

It doesnt seem to be affecting me when i go to 192.168.1.x:8181, only
localhost:8181. Are you running it behind apache?
On Aug 12, 2012 7:08 PM, "Begall" notifications@github.com wrote:

Also, my HTTP host is set to 0.0.0.0, so I guess that's effected too.


Reply to this email directly or view it on GitHubhttps://github.com/rembo10/headphones/issues/776#issuecomment-7675760.

Sorry but i am also getting this too. HTTP host is set to 0.0.0.0

Contributor

Begall commented Aug 12, 2012

Nope, it's running directly on my internal network. It's a Ubuntu 11.10 machine running Python 2.7, on IP 192.168.1.65. I ran the update command from a Win 7 machine on IP 192.168.1.64 with the latest Chrome as the browser.

I also just checked with a restart and the same behaviour occurs. In fact, it continues to try and redirect 192.168.1.65:8181 to 127.0.0.1:8181, even when that full IP is typed in, until the service is restarted on the command line, and then it's fine.

Edit: Actually, something strange happens with the service. When attempting to stop/restart it, it says:

start-stop-daemon: warning: failed to kill 18350: No such process
1 pids were not killed
No process in pidfile '/var/run/headphones.pid' found running; none killed.

This is despite it redirecting when going for that IP, so something is still running. going for sudo service headphones start fixes it, though.

Owner

rembo10 commented Aug 12, 2012

Gimme a couple of minutes and I'll get a fix up.

cptjhmiller: I suspect this is what's causing your other issue too

On Aug 12, 2012, at 7:24 PM, Begall notifications@github.com wrote:

Nope, it's running directly on my internal network. It's a Ubuntu 11.10 machine running Python 2.7, on IP 192.168.1.65. I ran the update command from a Win 7 machine on IP 192.168.1.64 with the latest Chrome as the browser.

I also just checked with a restart and the same behaviour occurs. In fact, it continues to try and redirect 192.168.1.65:8181 to 127.0.0.1:8181, even when that full IP is typed in, until the service is restarted on the command line, and then it's fine.


Reply to this email directly or view it on GitHub.

Thats what i was thinking, other wise i would have no said anything and just watched what happened here ;)

Owner

rembo10 commented Aug 12, 2012

See if the update fixes it

On Aug 12, 2012, at 7:44 PM, cptjhmiller notifications@github.com wrote:

Thats what i was thinking, other wise i would have no said anything and just watched what happened here ;)


Reply to this email directly or view it on GitHub.

Contributor

Begall commented Aug 12, 2012

Seems to have sorted it, thanks!

Owner

rembo10 commented Aug 12, 2012

Cool cool, thanks for the heads up
On Aug 12, 2012 7:55 PM, "Begall" notifications@github.com wrote:

Seems to have sorted it, thanks!


Reply to this email directly or view it on GitHubhttps://github.com/rembo10/headphones/issues/776#issuecomment-7676150.

And for me. Thanks rembo.

@Begall Begall closed this Aug 12, 2012

@santino405 santino405 referenced this issue in DobyTang/LazyLibrarian Sep 6, 2017

Closed

Localhost redirects to 127.0.0.1 #1023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment