Default url not bound to real IP

[chrisgla]

Getting a silly issue, not sure why

- http://127.0.0.1:8866 works
- http://192.168.178.230:8866/index.html works- and all other pages when full url given
- http://192.168.178.230:8866 doesn't work- 404 error

Had similar little niggles with first page not coming up before/ after login on a few different machines as I've been testing- they always work after I get first page and full page is given.

Any suggestions?

[mvallevand]

It seems you browser isn't following the redirect. You can use f12 to see what file is actually being requested

Martin

[chrisgla]

F12 gives:-

[color=var(--heading-color)]This 192.168.178.230 page can’t be found[/color]
No web page was found for the web address: http://192.168.178.230:8866/
[color=var(--error-code-color)]HTTP ERROR 404[/color]


If I clear cache I get login page:-
[color=var(--error-code-color)]http://192.168.178.230:8866/login.html?salt=6333089-00e0-4f75-81ca-629733397d[/color]

After login I get a blank white page with url
[color=var(--error-code-color)]http://192.168.178.230:8866/login.html?hash=bad111b22233344440b5014fb4cae186&remember=true[/color]

Happening on Chrome and new Edge, two different client machines and two different servers, all Win10


It's not a big issue as pages work by name- just wondered if others had seen similar.

[HarryH3]

IIRC, Chrome recently added a feature that automagically blocks double-forwards, as many are used to make it so that if you hit the backspace key to leave a page, you just get auto-forwarded right back to the page that you're trying to leave. I don't know why webmasters think it's a good thing to piss off site visitors, but it seems to be getting more common. Anyway, could that "feature" be somehow causing this issue?

I've noticed here that if I use Chrome to access NPVR from a different PC that I get a blank white screen after login. If I hit F5, then the page loads properly. Firefox just loads the page as I would expect.