mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
Upload: import: /photoprism/import/upload/123456789... does not exist #1187
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#1187
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @make-github-pseudonymous-again on GitHub (Oct 24, 2021).
TL;DR
What does not work as expected?
Upload ends with error. Files do not seem to be created in /photoprism/import and cannot be found in /photoprism/originals.
How can we reproduce it?
Upload a high quality file.
What behavior do you expect?
Should work.
Can you provide us with example files for testing or screenshots?
No.
What version you are using?
211018-e200f322-Linux-x86_64
Any other helpful information?
Example server log (newest first):
NGINX configuration:
@make-github-pseudonymous-again commented on GitHub (Oct 24, 2021):
Haha! Maybe NGINX is the culprit due to upload size constraint. I'll check if I can fix this.
@make-github-pseudonymous-again commented on GitHub (Oct 24, 2021):
Indeed. Fixed! I'll redact the issue to leave only the relevant information.