07-24-2017 10:56 PM
Ever since I installed Viveport - and reinstalled it - I've been getting a constant:
"An error has occured and the server could not be reached at this time. Please check your internet connection and try again later."
Well, my connection is fine, more so given I'm able to watch movies on Netflix or play some of my other game's online (including being logged into steam) I thought maybe the program required certain ports to be open to it but I can't find a list of ports that the program uses.
I've also done the following:
1. Disabled anti-virus, didn't do a thing.
2. Reinstalled program, didn't help at all.
This has been going on for a week now; I'm more than a little annoyed with how I keep getting this error yet am finding no solutions to the problem.
07-25-2017 09:48 AM
Did the error occur from the beginning or did it happen more recently? Also, can you check and tell me what version of Viveport you have and where you originally downloaded the software from?
07-25-2017 10:46 AM
Been that way from the very beginning, as far as version; that would be 1.0.8889 (r1076)
I've already checked for updates and found none.
07-25-2017 11:24 AM
Same problem here. I've been using my vive for a month now with steam VR without any problems. Thought I'd give Vive's desktop app a look, but I get the same error.
07-25-2017 08:26 PM - edited 07-25-2017 08:26 PM
Sadly when I click on 'report an issue' none of the options that are available really pertain to the issue I am having. I did prowl through the various issues to see if there is anything that I could try out, but nothing works. Viveport is also added to my firewall on the comp, but still the same issues. That's why I was hoping to find a list of ports that the program uses, to see if opening them up makes any difference.
07-27-2017 09:38 AM
Even if the issue doesn't seem relevant, if you follow through the steps, you'll be given a chance to create a log. Please do that.
08-01-2017 01:30 PM
Thanks, however, so far teh solutions they've given me do not work.. considering the page they pointed me to deals almost entirely with Chrome (which, so far as I can tell, has no bearing on the Vive app) guess I'll wait and see what their engineering team can come up with...
08-01-2017 01:40 PM
Which solutions have been provided? Just trying to follow along here.
08-07-2017 01:04 PM
Sorry, work has been a bit busy, only just now able to get on my comp to respond.
Sadly though I am still having this issue, and thus far no solutions to resolve it. The original support e-mail I got back on the 30th pointed me to a techinpost.com article in regards to a plugin, but the article largely dealt with Chrome (Which I rarely use, but still tried em anyway just for the heck of it) and even those solutions on that article that didn't deal with Chrome I likewise tried. Nothing has worked.
So right now I am pondering why it is taking support so long to get back to me on other solutions... although I'm also wondering why I was pointed to an article that really has nothing to do with the Vive software.
08-07-2017 02:41 PM
I PM'd you, if you could please respond there as well.
Did you reply to the original email explaining that the information they provided didn't help? What were their next steps?