I think we figured out the problem. We are doing "chmod -R 777 /opt/jboss/keycloak/themes" in the Docker file, but for some reason the jboss user gets a permission denied when trying to read our custom files (it reads keycloak and base themes fine). If we root into the docker container and manually change the file permissions, everything starts working as it should. So something is going wrong between the Docker build and Docker run of our keycloak app. We are working with our hosting provider to try to figure it out. -- Christopher Savory On 12/11/18, 10:18 PM, &quot;keycloak-user-bounces(a)lists.jboss.org on behalf of Chris Savory" <keycloak-user-bounces(a)lists.jboss.org on behalf of chris.savory(a)edlogics.com&gt; wrote: We upgraded our Dev and Stage keycloak instances about a month ago to 4.4 with no issues. Today we took the exact same docker container that is deployed in our staging environment and moved it to production. Our custom theme is loading on the login pages, but the theme is not selectable in any of the realm admin pages. We checked the database and the themes are set correctly in the realm table. What could be the issue? We are running in a clustered mode with two keycloak instances. -- Christopher Savory _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user