Skip to content
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

I can't upload some files - Server returned an unknown response. #1299

Closed
ghost opened this issue May 1, 2022 · 21 comments
Closed

I can't upload some files - Server returned an unknown response. #1299

ghost opened this issue May 1, 2022 · 21 comments
Labels
More info required Issue which will be closed under 14 days if not replied by the author

Comments

@ghost
Copy link

ghost commented May 1, 2022

Detailed description of the problem [REQUIRED]

While uplading, for random files lychee returns error saying:

filename failed
Server returned an unknown response. Please take a look at the console of your browser for further details.

Looking at the browser console, error looks like this - link

Steps to reproduce the issue

Steps to reproduce the behavior:

  • Drag and drop files to the lychee folder in browser
  • Repeating operation gives the same results for the same files, other files are imported correctly.

Screenshots

screenshot

Output of the diagnostics [REQUIRED]

Diagnostics
-------
Warning: Dropbox import not working. dropbox_key is empty.




System Information
--------------
Lychee Version (release):        4.3.0
DB Version:                      4.3.0

composer install:                --no-dev
APP_ENV:                         production
APP_DEBUG:                       false

System:                          Linux
PHP Version:                     7.4
Max uploaded file size:          600M
Max post size:                   600M
MySQL Version:                   10.4.19-MariaDB-1:10.4.19+maria~bionic-log

Imagick:                         1
Imagick Active:                  1
Imagick Version:                 1803
GD Version:                      bundled (2.1.0 compatible)


Lychee total space:              55.67 MB
Upload folder space:             9.00 B
System total space:              114.40 GB
System free space:               43.37 GB (37%)




Config Information
--------------
version:                         040300
check_for_updates:               0
sorting_Photos_col:              takestamp
sorting_Photos_order:            ASC
sorting_Albums_col:              max_takestamp
sorting_Albums_order:            ASC
imagick:                         1
skip_duplicates:                 0
small_max_width:                 0
small_max_height:                360
medium_max_width:                1920
medium_max_height:               1080
lang:                            en
layout:                          1
image_overlay_type:              desc
default_license:                 none
compression_quality:             90
full_photo:                      1
delete_imported:                 0
Mod_Frame:                       1
Mod_Frame_refresh:               30
thumb_2x:                        1
small_2x:                        1
medium_2x:                       1
landing_page_enable:             0
landing_owner:                   John Smith
landing_title:                   John Smith
landing_subtitle:                Cats, Dogs & Humans Photography
landing_facebook:                https://www.facebook.com/JohnSmith
landing_flickr:                  https://www.flickr.com/JohnSmith
landing_twitter:                 https://www.twitter.com/JohnSmith
landing_instagram:               https://instagram.com/JohnSmith
landing_youtube:                 https://www.youtube.com/JohnSmith
landing_background:              dist/cat.jpg
site_title:                      Lychee v4
site_copyright_enable:           1
site_copyright_begin:            2019
site_copyright_end:              2019
additional_footer_text:          
display_social_in_gallery:       0
public_search:                   1
SL_enable:                       0
SL_for_admin:                    0
public_recent:                   0
recent_age:                      1
public_starred:                  0
downloadable:                    0
photos_wraparound:               1
map_display:                     1
zip64:                           1
map_display_public:              0
map_provider:                    Wikimedia
force_32bit_ids:                 0
map_include_subalbums:           1
update_check_every_days:         3
has_exiftool:                    1
share_button_visible:            0
import_via_symlink:              0
has_ffmpeg:                      1
location_decoding:               1
location_decoding_timeout:       30
location_show:                   1
location_show_public:            1
rss_enable:                      0
rss_recent_days:                 7
rss_max_items:                   100
prefer_available_xmp_metadata:   0
editor_enabled:                  1
lossless_optimization:           0
swipe_tolerance_x:               150
swipe_tolerance_y:               250
local_takestamp_video_formats:   .avi|.mov
log_max_num_line:                1000
unlock_password_photos_with_url_param: 0
nsfw_visible:                    1
nsfw_blur:                       0
nsfw_warning:                    0
nsfw_warning_admin:              0
map_display_direction:           1
album_subtitle_type:             oldstyle
upload_processing_limit:         4
public_photos_hidden:            1

Browser and system

Lychee is hosted on docker container. Client is Firefox on Manjaro 21.2.3

@kamil4
Copy link
Contributor

kamil4 commented May 1, 2022

Realistically, you will need to reproduce this problem on the latest release (which is 4.4.0), or, even better, on the current git master, for the development team to pay attention. It's simply that the Lychee code base has gone through a large refactoring since 4.3.0, so error reports against such old versions aren't considered very relevant anymore.

BTW, your pastebin link doesn't work.

Since, as you say, this only happens with some particular input files, it would help tremendously if you could at least make one of these files available for us to download so that we can try it against the current development version.

Sorry if this is not the sort of answer you were hoping for...

@kamil4 kamil4 added the More info required Issue which will be closed under 14 days if not replied by the author label May 1, 2022
@Teku16
Copy link

Teku16 commented May 3, 2022

I am having the exact same issue on 4.4.0...

{description: 'Upload failed. Server returned an unkown error!', params: XMLHttpRequest, response: ''}description: "Upload failed. Server returned an unkown error!"params: XMLHttpRequest {onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, …}response: ""[[Prototype]]: Object
lychee.error @ main.js?1638565237:4989
xhr.onload @ main.js?1638565237:9202
load (async)
process @ main.js?1638565237:9138
(anonymous) @ main.js?1638565237:9267
n @ main.js?1638565237:21
upload.show @ main.js?1638565237:9046
local @ main.js?1638565237:9265
(anonymous) @ main.js?1638565237:3937
dispatch @ main.js?1638565237:2
v.handle @ main.js?1638565237:2
Diagnostics
    -------
    Warning: Dropbox import not working. dropbox_key is empty.

    System Information
    --------------
    Lychee Version (release):        4.4.0
    DB Version:                      4.4.0
    
    composer install:                --no-dev
    APP_ENV:                         production
    APP_DEBUG:                       false
    
    System:                          Linux
    PHP Version:                     8.1
    PHP User agent:                  Lychee/4 (https://lycheeorg.github.io/)
    Max uploaded file size:          500M
    Max post size:                   500M
    Max execution time:              200
    MySQL Version:                   10.3.34-MariaDB-log-cll-lve
    
    Imagick:                         1
    Imagick Active:                  1
    Imagick Version:                 1808
    GD Version:                      2.2.5

Stock installation. I am using cloudflare, but I have already tried turning the proxy off. Filesize does not appear to be a factor, and any uploads are failing, but I am seeing that the picture files themselves are being placed in their respective folders, and the application is able to access/change the MySQL database.

In the logs area, I get:

2022-05-03 13:54:54 -- notice  -- up -- 82 -- lychee_photos does not exist!
2022-05-03 13:54:54 -- notice  -- up -- 37 -- lychee_albums does not exist!
2022-05-03 13:54:53 -- notice  -- up -- 68 -- lychee_settings does not exist!

@nagmat84
Copy link
Collaborator

nagmat84 commented May 3, 2022

Are these the only messages? They originate from a migration, but are only notices. Aren't there any real errors on the log?

@nagmat84
Copy link
Collaborator

nagmat84 commented May 3, 2022

If you can please update to the head of the master branch. This probably won't solve the actual problem, but provide you and us with a much better error message.

@Teku16
Copy link

Teku16 commented May 9, 2022

I tried to email reply to this last week.. Sorry.. This is a fresh install. Where else should I look for errors?

@nagmat84
Copy link
Collaborator

nagmat84 commented May 9, 2022

A fresh installation of which version exactly? If you have installed version 4.4 again, it neither will help you nor us to find the issue even if it is fresh install. Please ensure that you have installed version 4.5 or preferably the head of master.

@Teku16
Copy link

Teku16 commented May 9, 2022

Sorry, I must be missing something. The releases page shows 4.4.0 as the latest version. I installed this, went through setup, and the errors above were as far as I got.

@nagmat84
Copy link
Collaborator

nagmat84 commented May 9, 2022

Version 4.4.0 is the latest, officially released version on Dec 3rd 2021. But the head of master has received 48 new commits since then. That is what @kamil4 wanted to tell you #1299 (comment).

Can you install the current master? Here is the documentation: https://lycheeorg.github.io/docs/#from-the-master-branch

As you have encoutnered the same error on two older versions of Lychee, the chances are high that it is not an undiscovered bug in Lychee itself but a configuration error of your server. I don't expect that the error will be gone with the newest version, but the newest version has significantly improved on the error reporting capabilities. So I hope that we will see a more specific error than "unknown response" which may tell us what is wrong.

@Teku16
Copy link

Teku16 commented May 9, 2022

I do not have the ability to use a command line on my hosted server. I had uploaded the files via FTP.

I tried installing via composer, but your scripts are written in bash. Thanks for the help so far, I guess I cannot use this software if I cannot get composer running on my server.

@nagmat84
Copy link
Collaborator

nagmat84 commented May 9, 2022

I assume we will release a new version soon. The big re-factoring was finished a week ago and we are currently only observing whether we see any bug reports from our users who are tracking the master branch closely. If the frequency of new bug reports is not significantly higher than usual, we will issue a new release soon.

I would be happy to have you as a user on board and hope that this little inconvenience won't push you away. If you can wait for two or three weeks that would be great.

@Teku16
Copy link

Teku16 commented May 10, 2022

I figured out how to install from master. Please see below!

 System Information
    --------------
    Lychee Version (git):            master (7a0c791) --  - Up to date (0 seconds ago).
    DB Version:                      4.5.1
    
    composer install:                --no-dev
    APP_ENV:                         production
    APP_DEBUG:                       false
    
    System:                          Linux
    PHP Version:                     8.1
    PHP User agent:                  Lychee/4 (https://lycheeorg.github.io/)
    Timezone:                        America/New_York
    Max uploaded file size:          500M
    Max post size:                   500M
    Max execution time:              200
    MySQL Version:                   10.3.34-MariaDB-log-cll-lve
    
    Imagick:                         1
    Imagick Active:                  1
    Imagick Version:                 1808
    GD Version:                      2.2.5
2022-05-10 15:06:30 UTC -- error   -- PDOStatement::execute -- 501 -- SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'legacy_id' at row 1
2022-05-10 15:06:30 UTC -- error   -- App\Models\Photo::performInsert -- 106 -- SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'legacy_id' at row 1; caused by
2022-05-10 15:06:30 UTC -- error   -- Illuminate\Database\Connection::runQueryCallback -- 712 -- SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'legacy_id' at row 1 (SQL: insert into `photos` (`updated_at`, `created_at`, `title`, `type`, `checksum`, `original_checksum`, `is_public`, `is_starred`, `album_id`, `owner_id`, `id`, `legacy_id`) values (2022-05-10 15:06:29.995371, 2022-05-10 15:06:29.995371, 165360-space_earth-earth-earthrise-space-canvas_wall_art-x750, image/jpeg, d5eaaf85ead57ed1d451d4ab863df44f341a3091, d5eaaf85ead57ed1d451d4ab863df44f341a3091, 0, 0, OYhdF7pBCdLDzcLzTPvs3BBk, 0, HNQ0Af3XI8R7vnM9A0D5fTru, 16521951899994)); caused by
2022-05-10 15:06:30 UTC -- error   -- App\Models\Photo::performInsert -- 106 -- SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'legacy_id' at row 1 (SQL: insert into `photos` (`updated_at`, `created_at`, `title`, `type`, `checksum`, `original_checksum`, `is_public`, `is_starred`, `album_id`, `owner_id`, `id`, `legacy_id`) values (2022-05-10 15:06:29.995371, 2022-05-10 15:06:29.995371, 165360-space_earth-earth-earthrise-space-canvas_wall_art-x750, image/jpeg, d5eaaf85ead57ed1d451d4ab863df44f341a3091, d5eaaf85ead57ed1d451d4ab863df44f341a3091, 0, 0, OYhdF7pBCdLDzcLzTPvs3BBk, 0, HNQ0Af3XI8R7vnM9A0D5fTru, 16521951899994)); caused by
2022-05-10 15:06:30 UTC -- error   -- App\Exceptions\ModelDBException::create -- 50 -- Updating photo failed; caused by
2022-05-10 15:05:54 UTC -- notice  -- App\ModelFunctions\SessionFunctions::log_as_admin -- 183 -- User (-snip-) has logged in from -snip-
2022-05-10 15:05:05 UTC -- error   -- App\Http\Middleware\MigrationStatus::handle -- 58 -- Database version is behind, please apply migration
2022-05-10 15:04:53 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:04:53 UTC -- error   -- Illuminate\Foundation\Http\Kernel::terminate -- 77 -- No application encryption key has been specified.; caused by
2022-05-10 15:04:53 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:04:53 UTC -- error   -- App\Http\Middleware\AcceptContentType::handle -- 61 -- No application encryption key has been specified.; caused by
2022-05-10 15:03:40 UTC -- error   -- ::file_get_contents -- 96 -- file_get_contents(/home/-snip-/-snip-/clients/Lychee/.env): Failed to open stream: No such file or directory
2022-05-10 15:03:40 UTC -- error   -- Illuminate\Foundation\Console\Kernel::handle -- 37 -- file_get_contents(/home/-snip-/-snip-/clients/Lychee/.env): Failed to open stream: No such file or directory; caused by
2022-05-10 15:03:13 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:03:13 UTC -- error   -- Illuminate\Foundation\Http\Kernel::terminate -- 77 -- No application encryption key has been specified.; caused by
2022-05-10 15:03:13 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:03:13 UTC -- error   -- App\Http\Middleware\AcceptContentType::handle -- 61 -- No application encryption key has been specified.; caused by
2022-05-10 15:03:10 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:03:10 UTC -- error   -- Illuminate\Foundation\Http\Kernel::terminate -- 77 -- No application encryption key has been specified.; caused by
2022-05-10 15:03:10 UTC -- error   -- Illuminate\Encryption\EncryptionServiceProvider::Illuminate\Encryption\{closure} -- 101 -- No application encryption key has been specified.
2022-05-10 15:03:10 UTC -- error   -- App\Http\Middleware\AcceptContentType::handle -- 61 -- No application encryption key has been specified.; caused by
2022-05-03 14:33:54 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 0x720)!
2022-05-03 14:33:54 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 0x360)!
2022-05-03 14:33:54 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:33:54 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 1920x1080)!
2022-05-03 14:33:54 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/9cbce1a31dbca3a90e04e10d376c9b07.jpeg
2022-05-03 14:33:54 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is 9cbce1a31dbca3a90e04e10d376c9b07.jpg
2022-05-03 14:30:19 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/66dbfdb15c15c28d093891157b6c2f2c@2x.jpg
2022-05-03 14:30:19 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:30:19 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:30:19 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/medium/66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:30:19 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/66dbfdb15c15c28d093891157b6c2f2c@2x.jpeg
2022-05-03 14:30:18 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/66dbfdb15c15c28d093891157b6c2f2c.jpeg
2022-05-03 14:30:18 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is 66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:14:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 0x720)!
2022-05-03 14:14:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 0x360)!
2022-05-03 14:14:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:14:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 1920x1080)!
2022-05-03 14:14:50 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/9cbce1a31dbca3a90e04e10d376c9b07.jpeg
2022-05-03 14:14:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is 9cbce1a31dbca3a90e04e10d376c9b07.jpg
2022-05-03 14:11:01 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/d5eaaf85ead57ed1d451d4ab863df44f@2x.jpg
2022-05-03 14:11:01 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/d5eaaf85ead57ed1d451d4ab863df44f.jpg
2022-05-03 14:11:01 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:11:01 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 1920x1080)!
2022-05-03 14:11:01 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/d5eaaf85ead57ed1d451d4ab863df44f@2x.jpeg
2022-05-03 14:11:01 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/d5eaaf85ead57ed1d451d4ab863df44f.jpeg
2022-05-03 14:11:00 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is d5eaaf85ead57ed1d451d4ab863df44f.jpg
2022-05-03 14:05:30 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/66dbfdb15c15c28d093891157b6c2f2c@2x.jpg
2022-05-03 14:05:30 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:05:30 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:05:30 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/medium/66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:05:30 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/66dbfdb15c15c28d093891157b6c2f2c@2x.jpeg
2022-05-03 14:05:29 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/66dbfdb15c15c28d093891157b6c2f2c.jpeg
2022-05-03 14:05:29 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is 66dbfdb15c15c28d093891157b6c2f2c.jpg
2022-05-03 14:03:50 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/d5eaaf85ead57ed1d451d4ab863df44f@2x.jpg
2022-05-03 14:03:50 UTC -- notice  -- App\Image\ImagickHandler::scale -- 113 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/small/d5eaaf85ead57ed1d451d4ab863df44f.jpg
2022-05-03 14:03:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 3840x2160)!
2022-05-03 14:03:50 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::resizePhoto -- 137 -- No resize (image is too small: 1920x1080)!
2022-05-03 14:03:50 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/d5eaaf85ead57ed1d451d4ab863df44f@2x.jpeg
2022-05-03 14:03:49 UTC -- notice  -- App\Image\ImagickHandler::crop -- 161 -- Saving thumb to /home/-snip-/-snip-/clients/public/uploads/thumb/d5eaaf85ead57ed1d451d4ab863df44f.jpeg
2022-05-03 14:03:49 UTC -- notice  -- App\Actions\Photo\Extensions\ImageEditing::createThumb -- 165 -- Photo URL is d5eaaf85ead57ed1d451d4ab863df44f.jpg
2022-05-03 13:54:56 UTC -- warning -- GenerateInstalledLog::up -- 18 -- Installation completed.
2022-05-03 13:54:54 UTC -- notice  -- up -- 82 -- lychee_photos does not exist!
2022-05-03 13:54:54 UTC -- notice  -- up -- 37 -- lychee_albums does not exist!
2022-05-03 13:54:53 UTC -- notice  -- up -- 68 -- lychee_settings does not exist!

We've definitely got some errors now.

@kamil4
Copy link
Contributor

kamil4 commented May 10, 2022

So did you create a .env file (messages from 15:03-15:05)?

Regarding messages from 15:06:30, please set the config variable use_32bit_ids to 1 (go to Settings, scroll to the bottom, click More) -- I believe that will fix it.

@Teku16
Copy link

Teku16 commented May 10, 2022

I did - those earlier messages look like what I was experiencing before coping and doing the .env, I dont remember having to do this the first install. Must have something to do with the release I used.

use_32bit_ids was the key! Photo success :) THANK you guys! Cant wait to try out the full platform now. I am excited; thank you both

@nagmat84
Copy link
Collaborator

I assume the issue can be closed?

@Teku16
Copy link

Teku16 commented May 10, 2022

Dunno-I was just piggybacking OP. Thanks again.

@ghost
Copy link
Author

ghost commented May 11, 2022

If you are planing a new release, I will test it again on the new release. I hope that you guys will prepare docker image for that. You can close that ticket for now, thanks.

@d7415
Copy link
Contributor

d7415 commented May 11, 2022

If you are planing a new release, I will test it again on the new release. I hope that you guys will prepare docker image for that. You can close that ticket for now, thanks.

The same fix may work for you. The Docker image for 4.4.0 has been available since January, or the :dev tag follows master.

That said, a new release will probably be coming soon.

@d7415 d7415 closed this as completed May 11, 2022
@ghost
Copy link
Author

ghost commented Sep 15, 2022

Unfortunatelly, changing use_32bit_ids to 1 didn't work in my case.

@nagmat84
Copy link
Collaborator

@s-kaczmarek Please open a new issue. If i understand you correctly, you are now using a different version than the one which the initial post of this thread is about. However, the detailed diagnostic and log output are required to properly investigate the problem. Hence, it leads to nowhere if you "re-use" old issues. Moreover, closed issued won't get much attention.

@megvadulthangya
Copy link

This issue is still dont fixed after 2 years... Or similar issue

freshly installed with docker compose with dockgee pulled latest image, no matter if i use cloudflare tunnel or just connect to my local address... (howewer when i try the hostname with cloudflare tunnel, i dont get any errors, just stuck the upload process
Screenshot 05-29-2024 10 56 49

@d7415
Copy link
Contributor

d7415 commented May 29, 2024

@megvadulthangya You replied to a 2 year old issue, the last post of which was "please don't just post on an old, closed issue".

I'm replying because just deleting your post will not tell you anything, but I will also be locking this issue.

@LycheeOrg LycheeOrg locked as off-topic and limited conversation to collaborators May 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
More info required Issue which will be closed under 14 days if not replied by the author
Projects
None yet
Development

No branches or pull requests

5 participants