Manual:How to debug/Login problems/ja

ログインやセッションの問題 (ログインできない、すぐにログアウトしてしまう、ランダムにログアウトしてしまう、「セッション データの喪失」エラーで編集できないなど) は、多種多様な原因があるため、デバッグが困難です.

エラーを調査・報告する際の注意点を紹介します.


 * エラーのさまざまな側面についての情報を収集してみてください:
 * ウィキ ドメインの Cookie を消去しても持続しますか? When logging in in incognito mode? When logging in with a different kind of browser?
 * If you use any ad blockers or browser privacy add-ons, are they blocking anything? Does it work if you turn them off?
 * Does it affect all user accounts, or just one?
 * Does the "remember me" flag make any difference? (Clear cookies before attempts.)
 * If the problems are happening on a Wikimedia wiki, try logging in on another wiki, preferably one that does not share a second-level domain name (so if the problem happens on xy.wikipedia.org, try for example xy.wiktionary.org).
 * If the problems are happening on your own wiki, what MediaWiki version do you use? (Session and login handling has been fully rewritten in 1.27.) Pre-1.27, check the value of ; if it is false, test that your PHP session handling is working (e.g. that  is writable). If it is true, see what session providers (  subclasses) you are using.
 * If the problems are happening on your own wiki, check what session backend is being used, and make sure it works (data is actually persisted between requests). The most safe configuration is . If you're unsure about how it's configured, add this setting at the end of your LocalSettings.php.
 * Please do not reuse old bug reports unless you are sure it's the same cause. There are lots of reports about past issues, and the while symptoms will usually look vaguely similar to yours (there are only so many ways login can fail) the cause is likely to be different.

Some additional checks:


 * Be sure is not set to 1 or true, otherwise PHP sessions will overwrite MediaWiki sessions.
 * Be sure is set to an empty string. It marks sessions as invalid if configured incorrectly.
 * If set, be sure and  are correct.
 * If is set to true, your webserver must be served with HTTPS.

If the above information is not enough to diagnose the issue (which is usually the case), you'll need to get detailed debug data:


 * Capture the relevant HTTP requests and responses (i.e. visiting the login page + submitting the login form + the resulting redirect; if the wiki uses single sign-on then all the requests to  as well). This can be done by using the Network tab in the Developer Tools of your web browser (more information: Firefox; Internet Explorer, Chrome and Chromium, Safari). Note this includes security-sensitive data (such as your session ID); when reporting bugs, either sanitize them or create a private paste. (Dumping to a HAR file is an easy way to log all required data.)
 * If the problems are happening on your own wiki, check your logs for relevant records, especially the,  ,  ,   channels. For certain types of cache you can get more information by setting debug mode: