After Manual upgrade I get: "The route public/api/v2/Gallery::Init could not be found." #3669
-
Lychee version6.9.1 Did you check the latest Lychee version?Yes, I did Which PHP version are you using?PHP 8.3 Detailed description of the problemI performed a manual upgrade from 6.8.1 to 6.9.1 today and received this error after the "Migrate!" phase. Steps to reproduce the issueNo response Diagnostics [REQUIRED]Unable to access Browser & System [REQUIRED]Vivaldi browser, windows 11 Please confirm (incomplete submissions will not be addressed)
|
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 13 replies
-
|
I just saw that someone else reported this issue. I apologize if this is redundant :) |
Beta Was this translation helpful? Give feedback.
-
|
Can you check your settings in your |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
OK, in the current running version on my server 6.8.1, I don't have an
ASSETS_URL in the .env file. The APP_URL and APP_DIR appear to be
correct. I can try to re-install and check these after. If it helps I
have attached the current .env file (with passwords and such removed)
…------ Original Message ------
From "Benoît Viguier" ***@***.***>
To "LycheeOrg/Lychee" ***@***.***>
Cc "brandonjacksonphoto" ***@***.***>; "Author"
***@***.***>
Date 9/4/2025 9:57:34 PM
Subject Re: [LycheeOrg/Lychee] After Manual upgrade I get: "The route
public/api/v2/Gallery::Init could not be found." (Discussion #3669)
APP_URL should still be your tld.
APP_DIR should be the /path/to/lychee
and ASSETS_URL should probably be tld/path/to/lychee.
—
Reply to this email directly, view it on GitHub
<#3669 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BQ744CXITIPD26HFG7ZKR2D3RCKS5AVCNFSM6AAAAACFJ7SVUWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZRGEZTMMQ>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
OK, so tried the manual upgrade again.. I get the same error. This time I noticed that the URL in the address field is now https://galleries.brandonjacksonphoto.com/public/public/public/ The two extra "publics" should not be there. soooo I did the following Edited the .env file and commented out the APP_DIR since this installation as at the root of the subdomain. Since I can get logged in now, I have included the diagnostics page below. Hopefully we can sort this out. Self-diagnosis:Info: Full directory permission check is disabled Info:Lychee Version (release): 6.9.1 Docker: false System: Linux exec() Available: yes Config:version: 060901 |
Beta Was this translation helpful? Give feedback.
-
|
And one more thing.. hopefully this is helping.. I edited the APP_URL in the .env file to APP_URL=https://galleries.brandonjacksonphoto.com/public adding the "public" at the end which has not been there in previous iterations and shouldn't be necessary as the install is at the root of the subdomain. When running this way all the thumbnails and images appear to work. When reviewing the diagnostics page I get several errors about the incorrect path which I have pasted below. Again.. hope this helps. Self-diagnosis:Info: Full directory permission check is disabled Info:Lychee Version (release): 6.9.1 Docker: false System: Linux exec() Available: yes Config:version: 060901 |
Beta Was this translation helpful? Give feedback.
-
|
I think I may have been the person that posted the other similar issue, and it was indeed solved by ASSETS_URL. Here are my .env file settings that would match that: for testing, you could comment out all of the above and try this, assuming it's on port 90, then access your site on http://(internal-ip):90 #internal testing settings one thing I would like is to be able to access the site from internal machines via ip directly, although now I wonder if the proxy setting would allow this? Need to test... |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate your input on this, however, your setup sounds different than mine. I'm not using dynamic DNS but also, by env file does not include the asset URL setting. I did try adding it but it didn't seem to help either. At this point I've rolled back to 6.8.1 to make sure my users can still access their images. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so I can try to apply similar settings to my .env and I assume the APP_DIR item should be blank as lychee is installed at the root. Otherwise I'll just leave it at 6.8.1 since it works fine there :) |
Beta Was this translation helpful? Give feedback.
-
|
I will try to investigate what is going wrong with the |
Beta Was this translation helpful? Give feedback.
-
|
OK, I'll run the update again today and I'll add the Asset_URL item again since it doesn't get added when I do the upgrade and isn't present in the current 6.8.1 installation. |
Beta Was this translation helpful? Give feedback.
-
|
nah, give me some time to test first, I'll get back at you. The Tells you that the default value is |
Beta Was this translation helpful? Give feedback.
-
|
@brandonjacksonphoto Can you check this? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I'm not sure I understand what you're asking me to do. If I need to replace my meta.php file.. the link in that conversation doesn't work (404). Plus I'm confused as this seems to be specific to installing in a subfolder, which mine is not. It IS installed in a subdomain so in a way it's a subfolder but Lychee is installed at the root of the subdomain. This was installed initially via Softaculous (Cpanel server) |
Beta Was this translation helpful? Give feedback.
-
|
The file is gone, because it is merged to master now. Also you do use the subfolder approach: you are not directly serving lychee to (and you should not even have |
Beta Was this translation helpful? Give feedback.
-
|
It is installed at the root of galleries.brandonjacksonphoto.com. I have sent a screenshot of the folder structure on the server: But, now that you mention it, I took a look at the .hataccess file and it has a redirect to the "public" folder in it (see below). I didn't add that but perhaps that's the problem? HTACCESS File |
Beta Was this translation helpful? Give feedback.
-
|
And the install details from the cpanel |
Beta Was this translation helpful? Give feedback.
-
|
in the |
Beta Was this translation helpful? Give feedback.
-
|
No, I cannot edit that. I can only remove the installation and reinstall it with "public" added to the path. If I try to edit the Directory field in the screen showing the installation details, it will error out as shown below. |
Beta Was this translation helpful? Give feedback.
-
|
Aw, that sucks :( |
Beta Was this translation helpful? Give feedback.
-
|
Well it works fine as it stands right now in version 6.8.1. It's only when I try to upgrade do I get the public/public/public problem. |
Beta Was this translation helpful? Give feedback.
-
|
I can. I need back it all up and install again. I thought it was bad to
install to a subfolder.
…------ Original Message ------
From "Benoît Viguier" ***@***.***>
To "LycheeOrg/Lychee" ***@***.***>
Cc "brandonjacksonphoto" ***@***.***>; "Mention"
***@***.***>
Date 9/18/2025 9:30:30 AM
Subject Re: [LycheeOrg/Lychee] After Manual upgrade I get: "The route
public/api/v2/Gallery::Init could not be found." (Discussion #3669)
The file is gone, because it is merged to master now.
https://github.com/LycheeOrg/Lychee/blob/master/app/View/Components/Meta.php
Also you do use the subfolder approach: you are not directly serving
lychee to example.tld you are serving it to example.tld/public right ?
—
Reply to this email directly, view it on GitHub
<#3669 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BQ744CUSLC2MS2CDJB4WMX33TJNRNAVCNFSM6AAAAACFJ7SVUWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBTHE2DEMA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That is not what I mean, yes it is bad to install into a subfolder. By setting directory to As a result you would not see the |
Beta Was this translation helpful? Give feedback.
-
|
I guess this is the way that the softaculous installer does the install. I can try at some point to do a completely manual fresh install from the latest version. |
Beta Was this translation helpful? Give feedback.
-
|
Resolved with 6.9.2 |
Beta Was this translation helpful? Give feedback.
Resolved with 6.9.2