Gigitsu
I’m currently working on implementing S3 external upload functionality for my project, following this guide. I want that any client-side error messages are properly handled and sent back to the server for further processing.
Reading the source code, I discovered that the UploadEntity error function takes in input the error reason. However, I’m unable to retrieve these error messages on the server side.
Upon inspecting the Upload module code, it appears that the reason for the error is simply discarded. Can anyone confirm if this is indeed the case? I’m looking for help on how to get these error messages on the server side.
Any insights or suggestions would be greatly appreciated!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sodapopcan
Just answering since you’ve gotten no bites yet.
Due to the fact that there is a default error message of “failed” on the client side, my guess is that that reason is always pretty generic. We’re chunking up to an S3 bucket so the only possibility for every day failure is a network error. We won’t be running out of space! Other possibilities like “account past due,” “missing API keys,” “bucket doesn’t exist,” etc are all things that you likely have ways of knowing immediately without having to wait for an upload to fail. Otherwise validations for things like file type and size are up to your own code before initiating the upload, so of course you have those errors.
This is just a hypothesis, though, as I’ve never looked into this myself—and maybe I’m missing something obvious? If you’re curious and are able to simulate an error, I would just hop into your deps directory and throw a
dbgon that line and see if it says anything useful.Gigitsu
Hi @sodapopcan , thank you for the answer.
In my scenario, users are responsible for configuring the bucket and providing credentials. Therefore, providing them with hints about why an upload is failing could be incredibly useful.
Moreover, since external uploads can be of any types, not limited to S3, I believe it’s importante to be able to capture the error message server-side and render them to the client via a live view for an optimal user experience.
I’ve opened this PR to address this issue
sodapopcan
Ah, that is helpful context! I figured you were just uploading some images to a bucket