Project

General

Profile

Actions

Bug #82118

closed

User interface does not react / 500 internal server error dummyToken

Added by Christian Weiske over 7 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2017-08-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The backend did not react anymore when clicking on backend modules or pages in the tree.

Opening the console showed me that ajax requests failed

http://localhost/typo3/index.php?ajaxID=%2Fajax%2Fusersettings%2Fprocess&ajaxToken=dummyToken
Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Those requests are fired when clicking in the backend.

The content of that ajax URL is

#1425389455: Invalid request for route "/ajax/usersettings/process"

When I open a new tab with the typo3 backend, I'm instantly logged in.
I do not know what caused this error; I logged in ~1h ago and did not use the backend for that time. When I tried to use it again, I found that problem.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #69763: Re-login after expired backend session throws exceptionClosedNicole Cordes2015-09-13

Actions
Actions #1

Updated by Christian Weiske over 7 years ago

  • Related to Bug #69763: Re-login after expired backend session throws exception added
Actions #2

Updated by Christian Weiske over 7 years ago

This is with TYPO3 8.7.4.

Actions #3

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from New to Needs Feedback

Is this issue still experienced on 8.7.9 or latest master?

Actions #4

Updated by Christian Weiske almost 7 years ago

No, but I haven't used TYPO3 8.x in the last months so often.

Actions #5

Updated by Sven Burkert almost 7 years ago

I'm also getting this error in TYPO3 8.7.9.
I can't reproduce it, but I'm getting hundreds of emails with this error (I've set "systemLog" to "mail,").
I'm not operating very long in TYPO3 BE, but the editors do.

Actions #6

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from Needs Feedback to New
Actions #7

Updated by Dmitry no-lastname-given over 6 years ago

Same issues on 8.7.16, I get tons of log entries like these -

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1425389455: Invalid request for route "/ajax/usersettings/process" | TYPO3\CMS\Backend\Routing\Exception\InvalidRequestTokenException thrown in file /opt/website/releases/1d76bf4149a8a986adf06fee730787d390e5da20/vendor/typo3/cms/typo3/sysext/backend/Classes/Http/RouteDispatcher.php in line 49. Requested URL: /typo3/index.php?ajaxID=%2Fajax%2Fusersettings%2Fprocess&ajaxToken=dummyToken

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1425389455: Invalid request for route "/ajax/context-menu" | TYPO3\CMS\Backend\Routing\Exception\InvalidRequestTokenException thrown in file /opt/website/releases/1d76bf4149a8a986adf06fee730787d390e5da20/vendor/typo3/cms/typo3/sysext/backend/Classes/Http/RouteDispatcher.php in line 49. Requested URL: /typo3/index.php?ajaxID=%2Fajax%2Fcontext-menu&ajaxToken=dummyToken&table=pages&uid=40&context=tree Changes in fields: bodytext.

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1425389455: Invalid request for route "/ajax/icons" | TYPO3\CMS\Backend\Routing\Exception\InvalidRequestTokenException thrown in file /opt/website/releases/1d76bf4149a8a986adf06fee730787d390e5da20/vendor/typo3/cms/typo3/sysext/backend/Classes/Http/RouteDispatcher.php in line 49. Requested URL: /typo3/index.php?ajaxID=%2Fajax%2Ficons&ajaxToken=dummyToken&icon=%5B%22actions-filter%22%2C%22small%22%2Cnull%2C%22default%22%2C%22default%22%5D

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1425389455: Invalid request for route "/ajax/system-information/render" | TYPO3\CMS\Backend\Routing\Exception\InvalidRequestTokenException thrown in file /opt/website/releases/1d76bf4149a8a986adf06fee730787d390e5da20/vendor/typo3/cms/typo3/sysext/backend/Classes/Http/RouteDispatcher.php in line 49. Requested URL: /typo3/index.php?ajaxID=%2Fajax%2Fsystem-information%2Frender&ajaxToken=dummyToke Changes in fields: l18n_diffsource.

Actions #8

Updated by Paul Keller over 6 years ago

I can confirm this issue with 8.7.16

Actions #9

Updated by Kurt Gusbeth over 6 years ago

Same problem in TYPO3 8.7.17:

Uncaught TYPO3 Exception
#1425389455: Invalid request for route "/ajax/context-menu" (More information)

TYPO3\CMS\Backend\Routing\Exception\InvalidRequestTokenException thrown in file
/usr/www/typo3_src-8.7.17/typo3/sysext/backend/Classes/Http/RouteDispatcher.php in line 49.

7 TYPO3\CMS\Backend\Http\RouteDispatcher::dispatch(TYPO3\CMS\Core\Http\ServerRequest, TYPO3\CMS\Core\Http\Response)

/usr/www/typo3_src-8.7.17/typo3/sysext/backend/Classes/Http/AjaxRequestHandler.php:

00164:         /** @var RouteDispatcher $dispatcher */
00165:         $dispatcher = GeneralUtility::makeInstance(RouteDispatcher::class);

00166:         return $dispatcher->dispatch($request, $response);

00167:     }

It is not possible to work with TYPO3 8.7

Actions #10

Updated by Kurt Gusbeth over 6 years ago

The Administration Log says to this error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1317178604: No file found for given UID: 24535 | TYPO3\CMS\Core\Resource\Exception\FileDoesNotExistException thrown in file /usr/www/typo3_src-8.7.17/typo3/sysext/core/Classes/Resource/ResourceFactory.php in line 382. Requested URL: http://dev.xyz.de/typo3/index.php?ajaxID=%2Fajax%2Fcontext-menu&ajaxToken=--AnonymizedToken--&table=tt_content&uid=24535 

Actions #11

Updated by David Bruchmann over 6 years ago

  • PHP Version set to 7.2

I just had this issue too in TYPO3 Version 8.7.16 with the impact that the backend never reacted anymore at all (at least the buttons I clicked).
I had the window open without working in it for a few hours but still could use the modal-window to login again.
After reloading the whole window it worked again.

Actions #12

Updated by David Bruchmann over 6 years ago

  • PHP Version deleted (7.2)
Actions #13

Updated by Kurt Gusbeth over 6 years ago

Note: in my case a bug in tika causes this error.

Actions #14

Updated by Sven Juergens over 5 years ago

same Problem here with TYPO3 8.7.24

@Kurt Gusbeth
can you say what exactly the problem with "tika" was .. and btw what is tika?

Actions #15

Updated by Christian Kuhn almost 2 years ago

  • Status changed from New to Closed

This is pretty hard to debug without more backtrace and timing information. Since the issue is quite old, I hope it is ok to close here for now and to wait for new issue reports with more detailed informatin.

Actions

Also available in: Atom PDF