Then why not tell us how because I want to know. You shouldn't ask for external help without posting the fix so people like me whoa re having trouble CAN FIX IT!Originally Posted by Johno
Then why not tell us how because I want to know. You shouldn't ask for external help without posting the fix so people like me whoa re having trouble CAN FIX IT!
Usually a vars error, it should be /swfs not /r63. Depending on where you put your swfs that is.
Sheenboys Emulator has backdoors i advise you not to use it. I suggest not
using a Cracked version of phoenix or use another emulator...
Just use the original one and set up your own license server it's the only thing i can advice at this moment don't use Sheenies because it's still full of backdoors and it's just causing trouble on your retro so don't try to waste your time and just the original one or just try to set up an r63B server for those who don't want to set up an Phoenix server.
Good luck to all and if you need help with anything just say so it's not hard to ask!
same problem here, i am working on my own cms and it does this
You need to set ip_lastforbans to 1, and check if there's any bans which is your hotel ip or proxy ip. Usually the problem as someone's used the :ipban command.
-_- I'm too kind.
Didn't fixed the problem for me, it worked when my ip was ::1 on localhost, and now it uses ip4 it does this...
I will test this, didnt realize that UDP have to be also portforwarded..
I'll just advice you to use the emulator with the class fixes because the cracked one by Sheenie and the other ones are mostly those who are having the most backdoors and cause many trouble for your hotel.
I'm using the original one and it's working fine for me.
found the problem.
Make shure first that the IP last gets updated everytime you load the client (the same for the sso ticket)
Then you also want to make shure (My problem) is that there will only be an sso ticket created when you load the client.
Yeah sorry I've set them both just in case.
Verstuurd van mijn GT-I9070 met Tapatalk
I don't see why people are still replying to this thread, the problem was solved since Johno posted... After that, there was no relevenace or need to post. Please close this thread moderator.
Regards
and hoe exactly is that supposed to be done?
Just check the CMS SSO ticket system. and fix it if that was the problem.
How to fix it?
Depends on what CMS you use,
just make shure those query's run and check if that code only runs when you are at the client.
Some PHP knowledge should be the key...
