Feature request: explanations for error notifications #11543
danielrosehill
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Hi, thanks for raising this. We are working on improving the output of the toast notifications to provide better information into the error rather than the code 500 you are seeing at the moment. At the moment you can open the dev menu in your browser to get a better idea on the error as a workaround at this stage. Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe
When creating a container throws up an error (for example code 500 which I think is due to using an unavailable port) it would be really great if clicking on the little info icon directed the user to (just an idea) a lookup reference of what the various error codes translated to.
Describe the solution you'd like
1: Portainer throws up an error
2: Portainer displays the error notification
3: (The ideas): Either clicking on the notification icon redirects to documentation or there's a bit more verbosity in the notification that gives you some more clues as to why the container wouldn't start
Describe alternatives you've considered
The current process is something like Googling the error number which inevitably brings me to a Reddit thread. It's fine but ... would be nice not to have to do that every time.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions