Session Verification Failed

[simfactor]

SMF Version: SMF 1.1.2
I have the same Session Verification Failed error also like in another thread. But how I got it is different.

Bear in my mind that I don't have a working website yet (let alone the domain name), I'm doing this on my development machine.

The scenario is this: users are able to log in, log out, and see some latest posts on Forum from another site with, probably, different domain.

I simulate that in my machine using different directory, let's say http://localhost/Site1 [nofollow] and http://localhost/smf [nofollow]. Using SSI I was able to do that scenario easily (thanks for the SSI guys! Really helpful!). However, when I clicked on the 'logout' button on Site1, I always get 'Session Verification Failed' error. But this error will disappear or not happening if I clicked the logout button on SMF.

Any way to fix this problem?

Thank you.

[simfactor]

No solution yet?

[metallica48423]

Are you using database driven sessions?

Anything in your error log?

[simfactor]

Yes, I'm using database driven session. And no error in mysql error log nor apache error log. Is there any log files for the SMF itself?

[SleePy]

Admin -> Error log is where SMF puts its errors it can catch.

So the site with the problems is the one that is through SSI? Did you configure the cookie settings correctly in server settings (I believe)

[simfactor]

Admin -> Error log is where SMF puts its errors it can catch.

So the site with the problems is the one that is through SSI? Did you configure the cookie settings correctly in server settings (I believe)

No error in Admin -> Error Log panel.

And yes, the site that having this problem is the one that call SSI functions (just welcome and logout so far). The cookies setting in SMF's Server Setting is:
- No local storage cookies
- Using independent sub domain cookies

[mikeafl]

I just fixed this error in my site. This may or may not apply to your situation. I wrap SMF in a template. SMF was trying to set a cookie, but  my template had already started output, so SMF threw a header error. I added a buffer and flush command in my template header and footer, respectively, and that fixed the SMF session problem. It remains to be seen what problems it's going to cause elsewhere, though.