-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unserialize(): Error at offset 2 of 11 bytes Error in 3.1.1 #271
Comments
hey @Brandutchmen thanks for the report! First of all, what database are you using? Please include the version as well. I haven't tested the Log Viewer with database as cache driver. In the meantime, could you switch Log Viewer to one of the other caching mechanisms, such as
I'll test the database cache driver later. |
Good call. Using either Plus, I should be using Redis for this anyway... Thank you! |
@Brandutchmen hey, what database were you using? MySQL, PostgreSQL, MariaDB, SingleStore? And what version? Just so I'm replicating in the similar environment. |
@arukompas, Mysql 8. |
I was also not able to get database cache driver so I just switched to file. |
same issue |
hey @Brandutchmen , there were improvements in latest Log Viewer, namely v3.1.8, could you try it again with database cache driver? |
i upgrade to newest version 3.1.9 but still have this error |
hey @MNhat0308 , are you using a database cache driver? Which database type and version are you using? Also, if you switch to a different cache driver, such as |
hi @arukompas , so i'm using file cache driver and postgresql version 13 |
Hello @MNhat0308, I'm facing the same issue. Could you please tell me how you resolved it? |
hi @irtzamazhar , i think you should upgrade to last version, i'm not using this anymore, so i don't know how to fix it/ |
@arukompas could you please help me to resolve this problem? |
@irtzamazhar please share the Log Viewer version, PHP version, Laravel version, Also, which cache driver are you using? If you switch to |
@irtzamazhar If you're not using Sanctum, you have to disable the EnsureFrontendRequestsAreStateful middleware in config/log-viewer.php. This middleware utilizes Sanctum's encrypt_cookies middleware if available; otherwise, it defaults to Laravel's EncryptCookies middleware. In Laravel's EncryptCookies middleware, serialize is false by default. |
In middle EncryptCookies file set |
Not sure what might be causing this. I'm trying to upgrade from 2.3
Full Stacktrace
The text was updated successfully, but these errors were encountered: