"Navigation to the webpage was canceled" in 1.8.1

louloizides · June 15, 2017, 8:26pm

Not sure what’s going on here but I just upgraded to 1.8.1 and I keep getting messages on multiple screens saying “Navigation to the webpage was canceled”. And it doesn’t seem to matter which page it’s coming from… I wasn’t getting this problem in 1.7.8. This is a big problem… any insight on how to fix it would be greatly appreciated.

Peter · June 16, 2017, 8:07am

Could you show us a screenshot of status window on the device when the issue occurs?

I assume there is no internet issues on those devices and that those pages can be accessed in IE11 without problems?

Could you also double check the browser emulation registry entries please - Enabling HTML5 in the Windows .net Player

louloizides · June 16, 2017, 11:01pm

Hi Peter,

I updated the browser emulation registry entries… it might have helped but I can’t tell yet as the one that was giving me the most issues just locked up. I’ll update this thread when I know for sure.

I can definitely send you the screenshot… but now sure what you mean by status window?

Also yes, they work perfectly in IE. The issue appears to be intermittent. Many times the IE windows will load the page fine. Every now and then it’ll say navigation canceled. One note about the pages - they do have Ajax and the ajax can take a while to load. So it’s possible they’re timing out.

Thanks,

Lou

louloizides · July 15, 2017, 6:17pm

This issue is still dogging me. It’s still intermittent but seems to be getting worse, and it doesn’t matter which page I put in the browser. The servers are local so there are no connectivity issues. What was the status window you were looking for -?

Peter · July 17, 2017, 8:05am

You can press ‘i’ on your keyboard to show status information on currently focused Xibo for Windows client.

Perhaps there might something you could tweak in IE internet settings or windows registry, I’m happy to look at those pages here in our office, assuming they are available over the internet, please send me your layout or links to the pages via private message.

louloizides · July 18, 2017, 12:03pm

Ok, I might be on to something. I saw in here that there are a whole lot of feature control keys besides emulation:

I think explicitly turning on AJAX might have helped… not sure why as it seems to be fine on some displays but not others. I need to give it another day before signing off on the issue, but I’ll update this thread when that happens.

Peter · July 18, 2017, 12:19pm

hm, in this case you could also take a look at IE internet settings -> security and adjust the ActiveX settings there, if those pages are using it. Other than that, perhaps that was indeed something with ajax there.

Emulated IE in Xibo should obey the settings from ‘normal’ IE11.

louloizides · July 19, 2017, 4:31pm

I dunno… still so far so good after that change… maybe I inadvertently changed something else that I missed. I also noticed that if the AJAX times out you get the nav canceled error, but that wasn’t happening on these pages.

It’d be great if a future client installation could give you the option to change these reg settings… at least until you guys find a way to integrate a newer browser (right now I can’t display anything from Grafana or Predix as they’ve both ended IE11 support).

louloizides · July 20, 2017, 12:19pm

I guess the reg settings didn’t work. The issue came back up again. When I came in this morning it was showing nav canceled errors… here’s the screenshot.

Here’s the latest log:

louloizides · July 20, 2017, 1:30pm

Actually I think I might have had one of those registry settings wrong and just fixed it… so will see what happens.

Peter · July 20, 2017, 1:32pm

Unfortunately the audit log messages, does not provide any insight about why it shows navigation cancelled there.

Perhaps indeed something was wrong with the registry edits you’ve made.

louloizides · July 21, 2017, 1:13pm

Unfortunately no luck… still getting the error. Really odd that it’s only happening in one of two clients on the same PC. I tried copying over the working one to the other though and it didn’t help.

The weird thing is that this is an internal site. No connection problems. And other Xibo clients around the plant (which I synced up the reg settings with) seem to display the pages ok.

Please consider handling the error in future versions: https://stackoverflow.com/questions/4223245/webbrowser-control-page-load-error

Since the pages updates via AJAX, as a mitigation issue I tried reloading the Xibo layout every couple of minutes. But I get the nav canceled error on every refresh. If I force the client to close and reopen the pages they work ok… then wait a day and it starts getting nav canceled errors again.

alex · July 21, 2017, 2:31pm

If you’re running two clients on the same PC, have you got them configured with different display settings profiles with different local webserver ports? If not, they’ll be conflicting and you will that these issues.

Also, I notice on your screenshot that XMR isn’t configured correctly. If you’re not running XMR, then you should leave the settings for that empty rather than filling in wrong values.

If you are running XMR, then you need to correct the XMR public address as it appears wrong, or the Player can’t connect to it, so check XMR is running, and any firewalls etc aren’t blocking the connection.

louloizides · July 21, 2017, 3:14pm

Hi Alex… ok that could explain a lot. I didn’t change the ports. Do I do that locally or through the CMS? Couldn’t find it.

Also I’ve never configured XMR (and I’m not even sure what it is) so I don’t know if I’m running it. The Xibo CMS is behind a firewall as we’re not allowed to run Linux servers on the local network so I do have to explicitly open ports to it. Right now I think I only have port 8080 open, which is what the Xibo CMS is running on.

alex · July 21, 2017, 3:27pm

Where you’re running two Players on the same PC, you need to create a different Display Settings Profile in the CMS for one of the two Players, that gives a different local webserver port.

You do that under Display Settings in the CMS. Once you’ve created the profile, assign it from the Displays page by editing the display and setting the different profile.

If you’re using Docker, then XMR will be running on port 9505. You need to enter the XMR address in the CMS settings page (XMR public address) as for example, tcp://server.domain.com:9505

If you’re not going to use XMR, then you don’t need the port open, and you should clear that field in the CMS settings so that the Players don’t try to connect.

louloizides · July 21, 2017, 3:31pm

Ok, yes I have two display settings profiles… one is necessary to get the player on the other screen as it has to be offset by a coordinate. Just changed the port for the whole lot… hopefully it’ll work