Error 310: Joyn, prime, netflix with 6.1.9.5 (It's fixed on server.)

SFBaysailor

Mine was working early this morning then the 310 error started showing up for Amazon and Roku. I tried deleting all data, complete uninstall and reinstall, didn't help. Hopefully servers will be up soon. I am on version 6.1.9.5

Wilson.Wang

Hi all,

It's fixed on server, please try it again.

Wilson

Sebastian001

Still error 310 for all providers. SF Servers still down.

@Wilson.Wang please give us an update
adrie

You have to give people time to fix it...

peter777

Obviously fixed! Thanks for that!:)
I tried Netflix, Prime and Joyn.

Chameleon

@Wilson.Wang Its also happening on Peacock.

zapt

Hi all,

It's fixed on server, please try it again.

Wilson
Wilson.Wang

Thanks so much!

In the future (assuming it's possible), it would be extremely helpful if either the StreamFab application or this forum could post a notification about such issues. It would save us a lot of unnecessary posts, deleting the Cache folder, downgrading to previous versions, reinstalling SF, messing with the OS, and general experimentation in order to try to correct an issue that has nothing to do with our current SF installation and that users cannot possibly fix.

Your previous post in this thread clearly informed me that there was nothing more to be done by users other than to wait, but it was buried in this thread. There are similar discussions occurring on Reddit and probably within other thread here in the forum, too. In my opinion, it would be better if you could just add a SF menu option, such as "Check for Known Issues', display such a notification automatically within SF, or create a new colored forum Sticky where everyone could quickly learn about such known fixable problems rather than having to scour forum threads for clues. Thanks.

Cats4U

The first reports of the 310 problem came into the forum at around 7am Eastern US time, which means that it was around 7pm in China. Wilson responded, saying they would check on it at 10:21pm China time. He then wrote back at 11:49pm China time to say it was fixed. I don't know about you, but I worked pretty much a 9 to 5 work schedule most of my life. 9am to 5pm. To the average eye, it would appear that Wilson went out of his way and handled everything in his off time. He should be thanked by all of us for the quick fix.

zapt

The first reports of the 310 problem came into the forum at around 7am Eastern US time, which means that it was around 7pm in China. Wilson responded, saying they would check on it at 10:21pm China time. He then wrote back at 11:49pm China time to say it was fixed. I don't know about you, but I worked pretty much a 9 to 5 work schedule most of my life. 9am to 5pm. To the average eye, it would appear that Wilson went out of his way and handled everything in his off time. He should be thanked by all of us for the quick fix.
Cats4U

Chill. I wasn't complaining about how it was handled or the speed with which it was handled. I was simply saying that having a uniform way of notifying users--in the app or in the forum-- would be appreciated. I reported it as a Support ticket two days ago. So the sooner we're all notified, the better. That's all.

Cats4U

Don't tell me to chill, or I'll see that you are extremely chilled here. As former moderator, I (along with Jack) was in charge of placing the banner notification. We placed it for long term problems such as the DRM change. This problem today lasted a total of about 4 hours and was taken care of by Wilson during his off duty time. He posted in the message threads that they were going to look into it, and then he posted that it was fixed. Not only did he post that within the threads, he edited the topic title to reflect the status of the problem. You didn't even have to open up the thread to know what was going on. He went above and beyond to keep everybody informed. You ask for a "uniform way of notifying users". That is what the forum is for, and he used it well. There was no need for additional notification.

« Previous Page