Unable to run pgadmin4 web version with reverse proxy using Caddy

When I try to run the web version of pgadmin4 behind the reverse proxy using caddy, the loading spinner comes and revolve continuously. The login page not come and hence unable to use pgadmin4 behind reverse proxy. While the login page is fully functional if I use my IP:PORT/pgadmin4

To Reproduce

Steps to reproduce the behavior:

1. Install Caddy
2. Add the config in /etc/caddy/Caddyfile (I have replaced the actual domain)

pgadmin.example.com {
        reverse_proxy 127.0.0.1:5433
}

where I have initialized my pgadmin4 server on 5433

3. Try to open the domain on web ideally the login page should pop up and the pgadmin4 is accessible
4. But below error message is shown on console of developer tool. And originally the spinner rotate for too long time and nothing really comes up.

Error message

[Error] Failed to load resource: bad URL (v4513226cdae34746b4dedf0b4dfa099e1781791509496, line 0)
[Error] Refused to execute https://pgadmin.example.com/pgadmin4/static/vendor/require/require.min.js?ver=91700 as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] ReferenceError: Can't find variable: require
	Global Code (login:54)
[Log] ReferenceError: Can't find variable: require — login:113 (login, line 123)
[Warning] Source Map "https://pgadmin.example.com/pgadmin4/static/js/generated/pgadmin_commons.js.map" has SyntaxError: JSON Parse error: Unrecognized token '<'

** Environment**

• OS: Linux
• pgAdmin version: latest
• Mode: [Server]
• Browser (if running in server mode): [chrome, safari]
• Package type: [DEB, Python, Container] attempted tests using these might impact other package type too.

Additional context
It is better if there should be a document section under deployment using reverse proxy using Caddy this will help most of the user running Caddy for there deployment.

Start with the Caddyfile configuration and the browser console errors, especially the failed require.min.js load and incorrect MIME type. Reproduce the deployment with pgAdmin on port 5433 and determine why the login page fails behind Caddy; done means the login page loads through the domain, and the deployment guidance covers this setup.