2 Easier Alternatives to NGINX Developers Can Use to Deploy Keycloak Behind a Reverse Proxy

Easier alternatives to overcome NGINX complexity with Keycloak

Photo by Antoni Shkraba: https://www.pexels.com/photo/man-in-gray-hoodie-using-macbook-pro-5475790/

Keycloak behind Caddy is much easier than using NGINX as a reverse proxy. And with NGINX Proxy Manager deployment turns into a no-code breeze.

Both solutions are the go-to if you’re struggling with NGINX. You could waste a lot of time on setting up NGINX to work with Keycloak. And face all of the possible known issues:

• Could not open Admin login page because mixed content
• Infinite spinner while opening the admin page
• KC_HOSTNAME_ADMIN doesn’t work

Let’s go over the alternatives to set up Keycloak behind a reverse proxy.

1. Nginx Proxy Manager

There’s not much to say about Nginx Proxy Manager. It’s a no-code setup and you’re up and running in seconds.

Here’s the related docker-compose.yml service:

npm:  
  profiles: [ "localdev" ]  
  image: 'jc21/nginx-proxy-manager:latest'  
  restart: unless-stopped  
  ports:  
    - '82:80'  
    - '81:81'  
    - '443:443'  
  volumes:  
    - ./data:/data  
    - ./letsencrypt:/etc/letsencrypt