CODEWITHSUNDEEP
phpyii2
Chloe
Chloe

Reputation: 26294

Yii2: Not Found (#404): Unable to find debug data tagged with '5578effb0790c4.13707485'

I'm getting this at the bottom of my page, where the debug bar should be. What is the problem?

This request: http://localhost:81/xxx/web/debug/default/toolbar?tag=5578f180963e82.28312577 is returning 404.

I need to see the error message & stack trace generated when I log to Yii::error(). It's not showing in runtime/log/app.log, so I need the debug bar.

Upvotes: 23

Views: 14644

Answers (8)

Harry P
Harry P

Reputation: 21

I got this error when using renderAjax and appending the resulting HTML to the tag of the page.

I simply appended to another element that wasn't the tag, such as and the error went away.

Upvotes: 0

srdjan
srdjan

Reputation: 41

Upgrade of yiisoft/yii2-debug library to latest(2.1.22) version resolved issue in my case.

Upvotes: 0

Raghavendra Prasad
Raghavendra Prasad

Reputation: 11

Give read/write/execute(777) permission to your project folder. This will work for you. It works for me.

Upvotes: 1

mae
mae

Reputation: 15664

Another reason for it not working is attaching HttpBearerAuth filter to the main application (not a specific controller). After removing the global filter, it suddenly works again. Not sure how to make it work with the filter. I will update this answer if I ever find a way.

Upvotes: 0

johnsnails
johnsnails

Reputation: 2031

I tried the info above without luck (and I suggest people here do the same, as in most circumstances it will solve your problem). But what worked for me was running. tail -f frontend/runtime/logs/app.log and it told me that there was an error with a table that it expected to exist but did not. Once I fixed that underlying issue my problem went away. In my specific case, I had the following enabled but no corresponding table/s.

'authManager' => [
    'class' => 'yii\rbac\DbManager',
],

Once I commented/removed it from my config, everything started working.

Upvotes: 5

leila
leila

Reputation: 551

i tried the removal of runtime folders but it didn't change a thing but a composer update fixed it for me

Upvotes: 0

robsch
robsch

Reputation: 9728

One reason could be missing write permissions for the runtime folder. The Debug Tool Bar creates there another directory debug which is used for *.data files.

This happens easily if the web server has its own user which differs to the user that has created the runtime folder.

Upvotes: 11

Alexey Muravyov
Alexey Muravyov

Reputation: 1153

I removed files from frontend/runtime/debug and frontend/runtime/cache and nothing was changed.

But when I removed all folders from frontend/runtime then it started to work.

Upvotes: 46

Related Questions