Page 1 of 1

"1301: Unable to contact verification server..."

Posted: 2014-12-16 20:00
by Bethovencore
Hey guys, I tried to log in today and got this problem for the first time.

"1301: Unable to contact verification server. Please check your internet connection and try again. "

I don't really know what happened cause PR was working fine yesterday...
I even reinstalled PR and logged in with a different profile but still doesn't work.

Can anyone tell me what the problem is or how to solve it?

Cheers! :(

Re: "1301: Unable to contact verification server..."

Posted: 2014-12-17 16:47
by Bethovencore
I was trying to log in and kept hitting play until somehow PR started updating. So I updated it and thought it might work now, but now there is this other error:

"1004: Error connecting to server. (10060)

Please help anyone?

Re: "1301: Unable to contact verification server..."

Posted: 2014-12-18 09:25
by meiz22
I get this pretty often, at least once a month, at first i thought it was happening after my internet was "shaped" but last time i was definitely at full speed. No idea what causes it or how to help really.

For me at least the issue always resolves itself, sometimes i only need to wait 10 minutes, sometimes a couple of hours and other times I've had to wait until the next day. Hopefully someone else can provide something more.

Edit: This being the error i'm talking about "1004: Error connecting to server. (10060)"

Re: "1301: Unable to contact verification server..."

Posted: 2014-12-18 11:32
by Bethovencore
meiz22 wrote:I get this pretty often, at least once a month, at first i thought it was happening after my internet was "shaped" but last time i was definitely at full speed. No idea what causes it or how to help really.

For me at least the issue always resolves itself, sometimes i only need to wait 10 minutes, sometimes a couple of hours and other times I've had to wait until the next day. Hopefully someone else can provide something more.

Edit: This being the error i'm talking about "1004: Error connecting to server. (10060)"
It ended up solving itself :smile:
This is really weird, but thanks for the reply!