log-viewer: Request failed with status code 500: Malformed UTF-8 characters, possibly incorrectly encoded

Hi. I’ve just replaced log-viewer 1.7 with 3.1 and re-published the vendor assets, but now I can’t view the Laravel log files which were working fine previously. I get an error message just under the search box saying: Request failed with status code 500: Malformed UTF-8 characters, possibly incorrectly encoded

Any suggestions?

About this issue

  • Original URL
  • State: closed
  • Created 9 months ago
  • Comments: 19 (8 by maintainers)

Most upvoted comments

hey @1YalcinSahin1 , @beard7 , your issue has been fixed in latest update, v3.1.7. You can now use database driver for cache and the contents should be UTF8-safe.

Still working on mail logs with attachments

hey @ale1981 , mail previews have been fixed in v3.1.8 😃 hope this helps!

that’s all from this bug report, I think. Let me know if anyone’s still experiencing “Malformed UTF8 characters” error after v3.1.8

Thanks, working now!

Thanks @arukompas You solved our problem quickly 😃

hey @ale1981 , mail previews have been fixed in v3.1.8 😃 hope this helps!

that’s all from this bug report, I think. Let me know if anyone’s still experiencing “Malformed UTF8 characters” error after v3.1.8