Timeline for err_connection_closed after 20 minutes when loggedin in backend
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2018 at 10:17 | comment | added | helle | I am looking for somebody who observed a similar problem and can say what he/she did then ... it is a problem I don't know and you Tom too. So maybe there is someone who does? | |
| Jul 16, 2018 at 10:14 | comment | added | helle | really :) that's what I am asking for ;) how to identify that one ... I would go further: if I can identify it, it will be 80% of the solution. | |
| Jul 16, 2018 at 9:52 | comment | added | Tom J Nowell♦ | Put simply the problem needs to be identified before it can be solved | |
| Jul 16, 2018 at 9:52 | comment | added | Tom J Nowell♦ | I understand, and I wouldn't expect anybody to go through an entire codebase anyway, you're going to have to conduct a process of elimination, commenting parts of that template out until it starts working again to see what the culprit is, or the reverse, uncommenting until it breaks. If it's an SSL issue etc you should be able to tell by visiting the page and seeing what the chrome network tools say. Otherwise I'm afraid there really isn't much more anybody here can do without getting their hands on the real deal and spending an hour or two debugging | |
| Jul 16, 2018 at 7:44 | comment | added | helle | It's hard to show code for me as the project is not public. And the code seems ok, because it works (on the test and local server the problem does not occure - so it's not neccessarily a code problem) and there are NO checks on the user-role or state in the code. So the question is ... how to debug such an issue on a higher level and pls. don't think I am new to php or wordpress only because of my 146 points here ... I asked the question because it is a real issue and hard to find where to start the highlevel debuggin. | |
| Jul 13, 2018 at 23:16 | comment | added | Tom J Nowell♦ | Without seeing code there really aren't many paths to check, look for conditionals that check if you're logged in that run on that page, and start commenting out code for that pages templates until it works again. You haven't finished the debugging process, and so you really don't know what your question is until you've isolated the cause | |
| Jul 13, 2018 at 22:22 | comment | added | helle | I really appreciate your input though, keep shooting | |
| Jul 13, 2018 at 22:21 | comment | added | helle | Yes yes... The limit is by 2 minutes... I am really stuck. | |
| Jul 13, 2018 at 21:25 | comment | added | Tom J Nowell♦ | What's on that subpage though? Have you done the standard disable all the plugins and themes and reactivate them one by one? WP_DEBUG? XDebug? Are you sure both production and your test server have the same versions of PHP etc? 23minutes is a very long time, double check your PHP time execution limit is a normal value most pages stop after 30s to 1 min as a top value | |
| Jul 13, 2018 at 21:20 | comment | added | helle | Yes I checked that. Nothing. No it's a subpage | |
| Jul 13, 2018 at 17:32 | comment | added | Tom J Nowell♦ |
Have you tried loading those pages directly to see what happens? Is there anything in your PHP error/warning log that might be related? Is /produktionen your WP root folder?
|
|
| Jul 13, 2018 at 16:02 | history | asked | helle | CC BY-SA 4.0 |