Bug #179
URL Key Mismatch
| Status : | Closed | Start : | 07/27/2008 | |
| Priority : | Normal | Due date : | ||
| Assigned to : | - | % Done : | 100% |
|
| Category : | Web Panel | |||
| Target version : | 1.3.1 | |||
Description
Hi there,
I just reinstalled everything on my mysql database and webserver with the new 1.20 Sourcebans, after configuring everything without a hitch I went to test a ban on myself, worked perfect, showed up on the banlist but when i tryed to click Unban or Deleteban, i get
Possible hacking attempt (URL Key mismatch)
Thanks,
Matt
History
07/28/2008 12:20 AM - Brad Smith
- Status changed from New to Feedback
Are you using a proxy on your local machine to access the website?
07/28/2008 02:17 AM - Matt Goldstein
No I'm not,
here is the link if it will help
[http://75.82.207.117/bans/]
07/28/2008 06:16 AM - Brad Smith
I cannot duplicate the problem. I will bring it to Olly's or Tsunami's attention tomorrow and see what they says. The key may not be matching because of the cache is not writing correctly. So just out of curiosity, can you check the "theme_c" directory permissions and make sure you have write to owner, group, and other. (0777)
07/29/2008 06:44 PM - Brad Smith
Is this still an issue? I checked your page and you are no longer banned.
08/03/2008 01:10 AM - Matt Goldstein
Im sorry ive been out of town for a bit,
Yes it is still a problem, i deleted myself from the mysql database to become unbanned.
08/08/2008 05:06 PM - Erik Minekus
I can't duplicate this either. Maybe you want to setup your SourceBans page again (add servers etc.) and give one of us basic access so we can take a look.
08/19/2008 03:15 AM - Jannik Hartung
if you open the page with &debug=1 in the url and unban s.b. - do you see the banlist_postkey in the session data? can you add a ban via webpanel?
08/21/2008 11:37 AM - Jannik Hartung
but the banlist_postkey isn't deleted. so open a page with &debug=1 after unbanning a person.. or define('DEVELOPER_MODE', true); in config.php ?
09/24/2008 11:53 PM - Jannik Hartung
- Priority changed from High to Normal
anything new for this?
do you have this issue with 1.3.5?