What app is this about, and its version: v7.6.0 What YunoHost version are you running: 12.1.40.1 What type of hardware are you using: Old laptop or computer
Describe your issue
Today I updated, through the YNH admin GUI, to version 7.6.0~ynh1.
Now, when I try to go to the Lychee instance, I get an exception 404. I restarted NGIX to see if the path would be recreated, but to no avail. I have rolled back to the previous version.
Any help with the update would of course be appreciated.
So this morning I did the upgrade again, went to the domain, etc that this app is for and got the 404.
Tried the domain name with /login at the end, and yes…I get the Lychee login page. Thank you very much.
The question is, of course, what do I need to do to get the upgraded version of Lychee to behave as it used to, ie just using the normal domain name to get to the gallery page? Hmmmm..
Yes, the app is in a PUBLIC path, https://derekjoneslighting.com/capture
I was able to log in with the admin credentials using:https://derekjoneslighting.com/capture/login
The error did not vanish.
I used three browsers with a cleared cache and history, same result.
I have restored the previous from backup, as it does get visitors.
As per @otm33 suggestion, I will move the instance to the root of a spare domain that I have to see if the issue persists.
I do have one question. How do I move the instance with its current domain to the root of a new domain? Deleting and restoring to the same place, I’m ok with, but if there is already a domain for the app, I’m a bit unsure about moving.
So @jarod5001 the latest update will only allow a root install to a domain.
I’m going to restore back to the original later this morning. I will leave the latest version version of Lychee at the above address so you can see that it works
The only thing that comes to mind is this commit that introduced path support in upstream but broke lychee package :
That I had to hack in a “temporary fix”
I just noticed that there is another commit to fix it upstream :
So may be removing that temporary fix can help.
I won’t be able to test it (I’m a little busy with work these weeks), so if you are able to test it on your instance, I would be grateful.
Here is the fix branch GitHub - YunoHost-Apps/lychee_ynh at fix · GitHub
Great, the original problem seems to be fixed, thanks to @otm33
For the warnings, it is related to the fact that there is a pending version waiting to be pushed to main and we were waiting for your feedback.
@jarod5001 fantastic… Going forward, should I revert to my backup and wait for the new version to be officially pushed, or is it safe to leave the instance as is?
