I’m hoping someone can assist a (relatively) new user regards Web Dashboard please!
Used Voyager in ‘demo’ mode only twice since obtaining last year thanks to poor weather, but following the my successful session the other night I was convinced enough for me to now obtain the ‘trial’ license so I can experience using it more fully, including to get to grips with the brilliant looking Web Dashboard, prior to pressing the credit card button for a full purchase!
And that’s my problem now - I’ve managed to set up and communicate with Viking using iPad via local server, Web Dashboard screen is displayed, but only a few text entry fields appear to be ‘active’ (e.g. enter IP address, password, etc.). None of the buttons seem to do anything, including the ‘connect’ button, so I’m unable to access Voyager itself or start anything up - Voyager is happily running correctly on a Windows mini-PC on same wi-fi network.
In the ‘Connection’ section I’ve left the IP address field blank, as per the user guide, as I’m on the same network. Entered user name/password as the default ‘admin / admin’ (same as in Voyager), but as mentioned the ‘connect’ (and, indeed all the other other buttons) appears to be non-operational so I can’t do anything else?
I’m guessing I’m doing something very silly indeed, or rather ‘not done’ - can anyone offer advice where I’m going wrong?
You are correct - I had Web Dashboard set to admin/admin in error instead of admin/password…
However, I have now tried setting both Voyager and Web Dashboard to using no password, using default password, changed password to something else (each time closing down and restarting Voyager and iPad after a change) but still the same! Again, no buttons seem to work, only text entries.
As far as I can tell, apart from my incorrect password error I’ve otherwise followed your advice and the Wiki tutorials exactly. But, of course I must still be doing something wrong I guess - odd how the Web Dashboard ‘buttons’ seem not to function, but would that be because it’s not actually ‘communicating’ with Voyager yet?
Thanks Leo … Yes, I’m sure I have application server running, also I’ve disabled firewall on mini-PC. I’ll check/try all settings once again and if I still can’t figure it out as a last resort I’ll post a request for remote support. Don’t wish to take up your valuable time with basic stuff, even if you are kind enough to offer remote support!
Thanks again for your assistance. I’ll be in touch, either way.
If you are on the same computer you can leave the IP address blank, but if you are on the same network, you need to put in the IP address or machine name that is running Voyager.
Well, I have an update - and I’m not sure if your kind offer of a remote session would be able to assist with this (unless you think otherwise)?! Hence I thought probably better to first of all provide this further update here before considering that. I’ll explain …
I’ve been successfully using my laptop to access mini-pc at mount remotely using Windows Remote Desktop for some time (Voyager is installed on mini-pc, Windows 10). I’ve now found that, using this laptop, if I enter the IP address into the box on Web Dashboard screen then I can connect successfully - even though I’m on the same local network and so as I understand it this should be left empty? But anyway, connection successful with laptop …
However, I’m still finding all of the buttons are ‘inoperable’ on my iPad when I try to connect in a similar way from that device - same issue as before, I can display the Web Dashboard screen but can only enter text (IP address, etc.), I can scroll up and down the screen, but none of the buttons will operate at all - nothing happens.
I realise this may now be a iPad compatibility issue I guess, rather than anything Voyager related, but any ideas why this should be the case? FYI, it’s a latest 4th generation iPad Air, IOS version 14.4.
Would like to solve this if possible, as being able to use my iPad with Web Dashboard is quite important to me!
Thanks for your advice - didn’t see your message until after I’d sent my last post. Seems I was confusing ‘localhost’ with ‘local network’ … my bad! That explains it, then.
Still odd the iPad won’t work, as I’ve described. Any ideas?
OK, I have a further update - I’m able to successfully access Web Dashboard from my iPhone, which is running on the same IOS version (14.4) as my iPad … I’ve also compared all relevant settings relating to network, privacy, and so on between those devices and as far as I can tell they’re exactly the same on both devices. But the iPad still flatly refuses to connect.
So, it seems the issue I have is somehow related specifically to the iPad Air itself - either some other obscure setting I haven’t considered, or even the actual14th generation version itself …??
Now I’m stuck - anyone else out there have any ideas what I can do now?
web dashboard work in all devices (if not so old) is written to be compatible with web device (is pure JS and HTML5), so this is not a question of platform but again some settings you have on the network or on the IPAD.
I’ve now obtained Firefox on my iPad, and I can confirm that connects to Web Dashboard perfectly without making any adjustments of changes to any settings.
So, thanks to George for that tip - he was absolutely correct!
Still, how odd that Safari on iPad will not connect, but Safari on my iPhone works fine?
Oh well - at least all seems to be working now, many thanks for your support and guidance.
Richard - I’ve got my iPad working fine - I wouldn’t conclude it’s a “Safari on iPad thing” (in fact I think the underlying Webkit engine is in common between them all).
Perhaps you’ve got different security features enabled on the iPad? The only way I can think of to be certain that it’s not a device specific configuration problem is to get another iPad OR factory reset.
Whatever the eventual solution, it woudl be great to put it into the Wiki - if I know anything about software, someone else will have the problem and your eventual solution will help others avoid diagnosing it themselves! Good luck.
I’ve tried what I believe to be every privacy and security setting I can think of on my iPad - but, I have to agree that something must be different of course, so maybe there is indeed something I’ve missed!
For the moment I’m not worried too much because Web Dashboard is working fine using Firefox. However, it would be good to figure out what the ‘problem’ is so that, as you say, it may help anyone else who faces this same dilemma.
Rest assured that if I do manage to find and resolve the ‘problem’ with trying to use Safari then I’ll report it back here for public information.
I’ve checked and double-checked all of my iPad settings compared to iPhone - identical. I’ve scoured the internet looking for possible explanations and/or solutions - no joy. What this searching has thrown up, however, is that the latest IOS14 upgrade seems to have introduced a raft of additional security features (some of them I believe out of users’ control), including some relating to local network access.
Granting permission for an app to access a local network location is now necessary … but, of course, because Safari isn’t a separate ‘app’ as such (it’s already built in to the IOS), it doesn’t appear on the ‘apps that have requested local network permission’ list. Hence, there’s no direct control over whether it’s allowed or not.
I also have a separate ‘stand-alone’ router designated solely for away-from-home imaging (no internet connection), and I now discover that neither device is able to connect at all via this router, but my Windows 10 laptop is able to connect quite happily using both this stand-alone router and my main internet-connected home router.
Bit of a blow because I was hoping to be able to use the iPad for any remote work when away from my home router, if I needed to … as it is, seems the only way I can get the iPad to communicate properly with Web Dashboard at the moment is when connecting via my home router, and only when using Firefox!
I’ve now reached the end of my expertise/knowledge in this area; if anyone out there has an inkling what might be going on here, I’d love to know!