|
Post by Renegade on May 31, 2010 9:42:52 GMT
What browser do you use, & did you have the same problem when your account was on server 3?
|
|
|
Post by Adrian on May 31, 2010 23:28:25 GMT
yeah had the same problem when i was on server 3....I have Firefox and my members varies between Google Chrome, Firefox, and Internet Explorer.
|
|
|
Post by Renegade on Jun 1, 2010 0:12:07 GMT
For the admin account you can increase the session time when you login to the admin panel. For user accounts, this can't be changed, but passwords should only need inputting once every two hours (I think? I'm not certain on the time for it). most browsers can be set to remember your password themselves anyway
|
|
|
Post by Adrian on Jun 1, 2010 2:21:47 GMT
where would that be?
|
|
|
Post by Renegade on Jun 1, 2010 9:11:23 GMT
THe number on the admin login page I've credited your account with some free subscription time
|
|
|
Post by Adrian on Jun 4, 2010 5:50:28 GMT
oh ok thanks =) I also added more to the subscription so hopefully things will be better. Since I paid a lot for it lol
|
|
Greg
Full Member
Posts: 136
|
Post by Greg on Jun 8, 2010 3:32:35 GMT
AYC - If the problem is just DNS propagation then that's up to your ISP and there's nothing at all we can do about it. On the plus side, it should fix itself if you can wait for your ISP to catch up. I was certain it was my ISP (or something with my service) rather than on your end. I finally got around to calling them last Friday. I got the annoying key prompts first. It took me all the way through (on my phone) where if I pressed a number it would reset my modem for me. I was so certain that wouldn't do it that I still stayed on the phone till I got a "real live talking" person. It loaded for him (which didn't surprise me since I was pretty sure it was more local to me). I'm not sure it is was simply a coincidence, something he did or the modem reset that was actually done on my phone but when he told me to try saybox.co.uk again (but with www which I still didn't use) it worked. Bottom line: It's all good now. Does that show any sort of patience on my part? P.S. You can call me all, @ll or Greg as I'm now known in PB Support.
|
|
|
Post by Renegade on Jun 8, 2010 6:45:56 GMT
It was a combination of both. One of the nameservers was listed incorrectly, but since we use three the other two should have taken over. It's anyone's guess why some ISPs didn't allow for that, because it's kind of the point of multiple nameservers. The reason it took so long to fix was because our domain registrar kept telling us there was nothing with the domain or the DNS, so we didn't find the error until we'd ruled out absolutely everything else, and I happened to decide to run a traversal report on it. For the arcades (not entirely related, but whatever) the DNS refresh was set to such a high rate that ISPs were ignoring it. i'm not sure how that happened, but we had the same problem of the registrar (a different one)telling us the domain was okay even their own tests were showing that it wasn't. The fast support times both registrars advertise seem to work by hiring lots of people to answer support tickets, but not actually training them
|
|
|
Post by Adrian on Jun 17, 2010 2:26:48 GMT
My SB isnt refreshing automatically now. and I paid for about 6 months worth.
|
|
|
Post by Renegade on Jun 20, 2010 2:26:40 GMT
Does this only happen with yours, or on any paid account?
|
|
|
Post by Renegade on Jun 20, 2010 17:25:16 GMT
We've found the problem. Our first attempt at a fix didn't work very well (actually it broke everything else) so give us another day or two to get it sorted
|
|
|
Post by Adrian on Jun 24, 2010 12:57:11 GMT
I'm guessing this hasn't been fixed yet huh.
|
|
|
Post by Renegade on Jun 25, 2010 9:23:37 GMT
I'm afraid not. However, its not been forgotten - autorefresh is a big selling point for the paid accounts, and not one we plan on leaving broken any longer than we have to
|
|
|
Post by Adrian on Jun 29, 2010 8:47:23 GMT
How long now cause I may just ask for my money back an all if this doesnt get fixed
|
|
|
Post by Renegade on Jun 30, 2010 11:08:48 GMT
We've spent the past couple of nights trying to find what's causing the problem. It definitely will be fixed, but its proving tricky to find exactly what's going wrong.
|
|