-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
V5: production.ERROR: Illuminate\Auth\Access\Response::authorize:151 This action is unauthorized. #2113
Comments
first you can try to add to your That should "resolve" some of your first bugs. What is the content of your
Actually you still can, the upper part (errors) of diagnostics is always accessible. |
You will also need to add the following folders in your
|
Great. I have:
But with the
|
The |
I should add I do not find a script |
No I meant in your list:
|
I do not have |
Ah, then they will be created as soon as you upload a picture. |
I imported an image but still no |
Weird, maybe only if you are using the Livewire front-end. |
BTW, here is the expected result using the Livewire front-end: https://lychee-demo.fly.dev/ |
I have some success with livewire after I modified my Apache configuration to contain:
Now the URL “https://images2.xxxx.xxx/livewire/livewire.js?id=f121a5df" returns the correct content. But I have problems with other links like Diagnostics that redirects to https://images2.xxxx.xxx/diagnostics instead of https://images2.xxxx.xxx/Lychee/diagnostics It looks like it is not possible to have Lychee installed in a sub-directory instead of the root when livewire is used :-( You can close the issue as I have a working solution: disable livewire. |
Well, I'm assuming that disabling livewire is only a temporary workaround that won't be supported forever? Personally I think it would be most unfortunate if this can't be fixed properly. In particular, I've always run Lychee in a sub-directory (whether in production or development). @ildyria what's your take on this? |
It would be great if serving in a sub-directory was possible. But that might be a tricky one to fix as this is most often on config side (nginx/apache) rather than backend php side. |
Do we have a sample apache configuration for support of Lychee in a sub-folder of the URI? |
Only this: https://lycheeorg.github.io/docs/advanced-setups.html#hosting-lychee-in-a-subpath-with-apache |
Ugly interface with truncated pictures
I upgraded from V4 to V5.
On the main page the connect button has no effect. So I can't access the diagnostics page.
If I enter an album I have only truncated pictures.
Upgrade to V5
I am not sure what I did wrong.
I use a custom script
lychee_migrate.sh
to upgrade Lychee.lychee_setup.sh
is:Output of the diagnostics [REQUIRED]
I can't access the diagnostics page because I can't login.
storage/logs/errors.log
contains:storage/logs/daily-2023-12-27.log
has the same content.In Firefox I also get a 404 error:
On my server Lychee is installed in
/Lychee
not in/
. So I am not really surprised to get strange errors and behavior.The correct URL is https://images2.xxxx.xxx/Lychee/livewire/livewire.js?id=f121a5df instead.
Browser and system
The text was updated successfully, but these errors were encountered: