Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Optional
    • Resolution: Rejected
    • Affects Version/s: 10.0.2
    • Fix Version/s: None
    • Component/s: Admin - Console
    • Labels:
      None
    • Story Points:
      1
    • Steps to Reproduce:
      Hide

      1. start an instance with docker
      ```
      docker run --name kc -d -p 8080:8080 \
      -p 2346:8443 \
      -e KEYCLOAK_USER=admin \
      -e KEYCLOAK_PASSWORD=admin \
      -e PROXY_ADDRESS_FORWARDING=true \
      -e KEYCLOAK_FRONTEND_URL=https://auth.mydomain.com/auth \
      jboss/keycloak
      ```

      2. configure nginx reserve proxying with follow config
      ```
      server {
      #listen 80;
      listen 443 ssl;
      server_name auth.mydomain.com;

      ssl_certificate /etc/letsencrypt/live/auth.mydomain.com/fullchain.pem;
      ssl_certificate_key /etc/letsencrypt/live/auth.mydomain.com/privkey.pem;

      location /

      { proxy_pass http://127.0.0.1:8080; proxy_set_header Host $host:80; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }

      }
      ```

      3. visit this instance an login admin conosole successfully
      4. refresh the page

      Show
      1. start an instance with docker ``` docker run --name kc -d -p 8080:8080 \ -p 2346:8443 \ -e KEYCLOAK_USER=admin \ -e KEYCLOAK_PASSWORD=admin \ -e PROXY_ADDRESS_FORWARDING=true \ -e KEYCLOAK_FRONTEND_URL= https://auth.mydomain.com/auth \ jboss/keycloak ``` 2. configure nginx reserve proxying with follow config ``` server { #listen 80; listen 443 ssl; server_name auth.mydomain.com; ssl_certificate /etc/letsencrypt/live/auth.mydomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/auth.mydomain.com/privkey.pem; location / { proxy_pass http://127.0.0.1:8080; proxy_set_header Host $host:80; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } ``` 3. visit this instance an login admin conosole successfully 4. refresh the page
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Hi there!
      I got an 502 error when refresh admin console page.
      After clean the cookies I can login and access admin console again
      The request does not hit keycloak instance according to the logging.

        Gliffy Diagrams

          Attachments

          1. kc14373-compose.yaml
            0.4 kB
          2. nginx.conf
            0.4 kB

            Activity

              People

              • Assignee:
                aszczucz Alex Szczuczko
                Reporter:
                raphaelsoul Dechen Zhuang
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: