302 after setting up wrong route
I have made my test installation unusable by messing around with routes. In the dashboard, I tried adding a route for /entry
/signin with a 302 but I did it completely wrong and got an unresolvable loop at
a) So I deleted that route line from my config.php and expected that everything would be alright, but the loop still was there. I laughed at myself because I forgot to delete the ini files, but to my surprise, deleting them did not change anything!
b) I have adminer in one other subfolder of the same domain, and that's why I thought "If I can't fix it, I will avoid it!" and I simply renamed the directory, changed the nginx config to point to the new folder, restarted it and cleared the cache. I've tried that two times already, but there's still no change. My access log is full of lines like that:
... "GET /VaTe/entry/signin?Target=entry%2Fsignin HTTP/1.1" 302 5 "-" "Mozilla...
c) I've downloaded current 2.1 again and copied it over to my installation. No effect.
I have no idea why that is happening and why I can't solve that. b) made me think that it must have something to do with my Vanilla installation, but then c) must have solved it.
Does anyone has any clue?