quda
I need to return a custom error message (json) for Internal Server Error.
The message is needed for explaining some error causes such as: corrupt file, internal path not found, bad json, python script execution error etc.
The 500 error would be raised in certain places in my Phoenix web API code when such upstream errors/exceptions occurs.
In the official doc is not clear how exactly to do this.
Thanks for help!
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
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










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dopomecana
Will this work for you?
quda
Thanks but not really… different context, cannot use conn there
I need something to “raise”:
raise MyApp.MyCustomError {<code>, <msg>}more exactly:
raise MyApp.MyCustomError {:500, "Script xxx.py did not execute successfully"}I think you got the idea.
dopomecana
have you tried to just return a map? I got the idea from here
mcrumm
Review the Custom Exceptions section of that same guide.
You will need a
defimpl Plug.Exceptionif you want your exception to be rendered as an HTTP response through Plug.If you want to render your custom error in production, you will also need to add a pattern match to the
render/2function on your ErrorView. To ensure this is working correctly, you may want to setdebug_errors: falseon your Endpoint config indev.exs.
Edits: typos
quda
Thanks, I eventually managed to do it with defimpl.
I’m writing here the solution, it might help others with similar issues:
In the myapp_web.ex:
error_view.ex:
.Finally, in my code:
Cheers,
T.
arcanemachine
I dug into this, and found it can be simplified a bit when defining the exception.
lib/your_project_web/custom_500_error.exlib/your_project_web/views/error_view.exlib/your_project_web/controllers/some_controller.exNote that when calling exceptions, you can also pass arguments to it as a keyword list. For example, this would work:
raise YourProjectWeb.Custom500Error, message: "Hello world!"Since we defined the
plug_statuswhen we created the exception, you could also override this if you wanted to make a more generic exception handler:raise YourProjectWeb.CustomResponseError, plug_status: 400, message: "Hello world!"From what I understand, you would need to make sure you added a clause to
)
error_view.exfor each status code you added. (I found some workarounds when I was looking into this, but they seemed kinda hacky. Left as an exercise to the reader