Currently if the charm is configured to connect to an external avatar service by an admin in the settings, it needs to be able to reach avatars.discourse.org. If it can't, it should warn about that. Currently there's no indication, and the only way you'd know is that avatars fail to render.
To Reproduce
Deploy the charm somewhere that doesn't have access to avatars.discourse.org
In the admin interface set "external system avatars enabled" to true, and "external system avatars url" to /letter_avatar_proxy/v4/letter/{first_letter}/{color}/{size}.png
Bug Description
Currently if the charm is configured to connect to an external avatar service by an admin in the settings, it needs to be able to reach avatars.discourse.org. If it can't, it should warn about that. Currently there's no indication, and the only way you'd know is that avatars fail to render.
To Reproduce
true
, and "external system avatars url" to/letter_avatar_proxy/v4/letter/{first_letter}/{color}/{size}.png
Environment
Charmed Kubernetes, Juju 3.1.7
Relevant log output
Additional context
No response