The default logo configuration in application.yml includes a relative path to an image within the application.

# Allow users to customize logo image url as well as label
logo:
    url: "/assets/openboxes_logo_40x40.jpg"
    label: ""

Because the logo image does not exist under the configured path, Tomcat returns a 404 error and subsequently, the application does not render the logo image properly

We, as developers, haven't noticed this very often because most of our existing production and test servers have configuration that overrides the default logo using a custom logo hosted on a separate server.

Like this ...

openboxes.logo.url = "https://obdev3.pih-emr.org/images/pih_2020_logo.png"

However, it becomes glaringly obvious when you install a new server with default configuration and see the broken image.

Approach 1
The easiest way to solve this is to hard-code the context path in the logo URL as highlighted in our configuration guide on this topic.

logo:
    url: "/openboxes/assets/openboxes_logo_40x40.jpg"

Approach 2
A more ideal solution would be for the application to automatically add the context path in cases where it's needed either within the application.yml

logo:
    url: "${self:custom.globalSchedule}/assets/openboxes_logo_40x40.jpg"

Approach 3
or in the API that gathers the configuration for the application.

def logoUrl = location?.logo ? "${createLink(controller: 'location', action: 'viewLogo', id: location?.id)}" : grailsApplication.config.openboxes.logo.url

The second part of this is the one that's problematic. We need to wrap this configuration with something that adds the context path, i.e. using something like the createLink taglib.

${createLink(url: grailsApplication.config.openboxes.logo.url}

For now, we are going to use the hard-coded fix to avoid a more time-consuming and potentially error-prone solution. But Approach 2 would probably be the best in the long-run.