I can't upload files.
Hi!
I managed to start ente server on a wm with proxmox using ubuntu server os.
I can reach the web page on port 3000 and i was able to log in on pc, and i was able to connect with my phone as well through the app, but when i tired to upload my images its got stuck and no file uploaded...
17 Replies
Remember to use /solved to mark your thread as solved once your question is answered.
Can you check the browser console via browser dev tools. There might be some errors logged there that can explain why uploads are not working. Got my ente instance up and running earlier, but before that I was having issue with uploads due to cors.
Yeah.. i should have looked at the console in the browser, but now i still don't know whats the problem
I"m having a similar issue, but i'm using the Ente desktop app to connect to my self-hosted instance of Ente. Am I able to use the webapp without having to build it ?
If you used the quickstart script, locate the minio-data folder and verify that the bucket folders were created. If not, you will need to modify your docker-compose.yaml file and remove the post_start section and replace with minio-provision.
https://help.ente.io/self-hosting/troubleshooting/docker
Docker Errors | Ente Help
Fixing docker related errors when trying to self host Ente
I switched to using the quickstart script and modifying the musuem.yaml file endpoint section
I had to change the endpoint to use my IP instead of localhost and it worked fine
I did the same for the
ENTE_API_ORIGIN key in the compose.yaml fileThanks for the help! I changed the musuem.yaml changed localhost to 0.0.0.0 and now its works on pc, but on phone on browser i can upload images but i cant see them, and in the app i still can't upload or see the images what i uploaded from the browser... i can reach the port 3201 and i can download the encrypted files from Minio.
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Are you still having this issue and did you update the compose.yaml file ?
Oh sorry if you’re hosting directly on a Linux machine. I believe the compose.yaml file only applies to the docker setups. Correct me if you are hosting with docker or not ?
Hi! Yes, i still have the issue... I'm trying to host on a VM, and i use "docker compose up" to start.
I'm having the same issue, everything goes as normal but as soon as I try and upload something it's like it gets bricked
Stumbled in here also looking for a solution to the upload failing problem. I'm running the server on a local network machine. I installed it by following the quickstart process. I'm not sure how to proceed. One thing I tried is replacing the
post_start hook with minio_provision as suggested by @SuperD9241 but it doesn't seem to make any difference. I cannot see anything unusual in my logs. MinIO is up and running and I can login. The minio web ui says the buckets were created, but my data folder is empty.
I should say, when I try to install the server on my local machine, uploads work fine
Does anyone have any suggestions, please?
Reading a bit more in this thread, I tried updating the endpoint in museum.yaml as suggested by @ibz096, from localhost to the name of the machine which hosts the server. That seems to have fixed it!
Thank you @ibz096 !
Excited to try out this very cool looking app (thank you devs!)
it might make sense to update the website documentation about this issue (self-hosting guide)
Another solution could be to populate the endpoints with the hostname of the machine, rather than localhostI’m not a developer but if it was the hostname of the computer there would have to be an assumption that there is some kind of DNS or mDNS implementation on your local network. If there were clear documentation steps it would good
@RdL were you able to resolve the issue on your end
I did this change as i wrote, and its works on pc from the browser but not on my phone not from the app neither from the browser... i also cant see already uploaded images on phone, i only see the folders.
Should i open a new thread for this issue, because seemingly the main problem for most of the users is fixed by editing the .yaml file renaming localhost to 0.0.0.0 ...?
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Do you want to setup a call and troubleshoot ? We can do it over discord ?
Just let me know when you are free and we can jump over to one of the voice channels on this server