-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
can't backup #18
Comments
This is from a RaspberryPi 400, correct? In the Nginx message, did you masked the server address as xxx.xx.x.x? |
Can you try 'sudo chown -R yourusername:yourusername ~/immich/server/upload' |
from the raspberry pi400 yes |
@ippocratis Can you try
I remember having this issue once out of nowhere and that is how I fixed it. Just curious, shouldn't the server in the container has an IP address of |
i have no idea whats goin on for the ```http://immich_server:3000`` part i left the 3000 port unchanged in the docker-compose.yml if i understand correctly what you mean if i try to reach the adress in a browser it says site cant be reached
|
The file won't be copied to your local Did you build the mobile app directly or use the APK? If you use the APK, please try a different APK here. From the root of the directory |
updated with the progress i thought earlier was probably a misunderstanding from my side , my bad most likely i messed something up thanks... |
No worry, I think you are very close. Unfortunately, I don't have the pi400 to try this on, otherwise, I can help you with better information. Let me know how it goes! |
Can you clone the repo to the new location, in server folder you create the upload directory first. Then you run the docker compose up command? |
@ippocratis I want to let you know that I can replicate your problem and is working on the fix. |
@ippocratis I updated the docker-compose file. I was always running my development environment as root so I didn't encounter the problem when using volume mount (docker managed directory), once I switch to a non-root user, then I have that issue. The solution I came up with is to use bind mount (mount directly to a directory on your file system) and let the user specify where they want to store all of the access on their local machine in the Let's say you create a directory |
yep working fine now |
i chmod -R 755 ~/immich/sever/upload
The text was updated successfully, but these errors were encountered: