SMF Support > SMF 2.0.x Support

Secound issue in 4 days with smf :(

<< < (2/2)

MrPhil:
S2iqBM.jpg seems to be showing the "White Screen of Death". That usually means there's a fatal PHP error somewhere. Look at the page source in the browser to see if there's an error message or any partial page lurking in there. Look at your hosting system error log to see if it reports anything. Look for "error_log" or similar files in your SMF directories. Go into phpMyAdmin and browse the SMF log_errors table (if you can't get to the point in admin to view it). Somewhere in all of there should be something that says what broke.

If it was working fine and suddenly died, did your host make any system changes at that point, that they'll fess up to? The only other possibility is that a hacker got in and added code to your site, but they screwed up and it's crashing the SMF code. Look at your files and see if there was anything last modified around the time the errors started. Look inside those file(s) and see if any code has been added (especially at the very beginning or end).

viperpray:
I have not changed anything befor the error. As for the error logs i tried them first.
like here is the link it gives me
http://pokemonium.com/forum/index.php?PHPSESSID=4793763154857a5dc1a38f645bbed554&action=login2 [nofollow]

this link does not work now if i remove: &action=login2

so we just have
http://pokemonium.com/forum/index.php?PHPSESSID=4793763154857a5dc1a38f645bbed554 [nofollow]

this url will work

MrPhil:
A PHPSESSID value is good only for the one particular session. You should not be trying to reuse it (if that's what you're trying to do).

http://pokemonium.com/forum/index.php takes me to your forum's front page. Are you saying that no one can log in at that point? I believe that the action=login2 is for a retry on a bad ID or password.

The WSOD, if it's still happening, needs to be dealt with first. As I said, it indicates a fatal PHP error. The exact error should be logged somewhere (in the page source, in your site error log, or in an error_log type file). If it worked OK for 4 days, and neither you nor your host made any changes, odds are that a hacker inserted some code. Look at the "last modified" time/date on all your files and see if there is anything suspiciously recent. If there is, look carefully in those files.

Navigation

[0] Message Index

[*] Previous page