pomerium: v0.21.x and 0.22.x not working on synology docker

What happened?

After upgrading to v0.21.x I get “This page isn’t working” error (HTTP Error 500) when trying to connect to my docker containers, for example going to

https://heim.carmaXXXX.xyz

In my policy file this address is linked to my heimdall container, the same for any other container, i.e. qbittorrent

What did you expect to happen?

In v0.20 or earlier when going to https://heim.carmaXXXX.xyz I am presented with my identity provider service (okta) and after entering my credentials I have access to any of my docker containers.

How’d it happen?

  1. Ran heim.carma.xyz
  2. Saw error “This page isn’t working” error (HTTP Error 500)

What’s your environment like?

  • Pomerium version (retrieve with pomerium --version):

      v0.21.2 (but also with other v0.21
    
  • Server Operating System/Architecture/Cloud:

             synology DSM7 7.1.1-42962 Update 4 (newest)
            docker 20.10.3-1308 (newest)
    

What’s your config.yaml?


I use docker-compose:

    pomerium:
        container_name: pomerium
        network_mode: bridge        
        environment:
            - POLICY=xxxxx
            - IDP_CLIENT_SECRET=xxxxxxx
            - IDP_CLIENT_ID=xxxxxx
            - IDP_PROVIDER=okta
            - COOKIE_SECRET=xxxxxxx
            - AUTHENTICATE_SERVICE_URL=https://authenticate.carmaXXXX.xyz
            - INSECURE_SERVER=TRUE
            - IDP_SERVICE_ACCOUNT=XXXXXXXX
            - IDP_PROVIDER_URL=https://dev-XXXXXX.okta.com
        ports:
            - 32443:443
        restart: unless-stopped
        image: pomerium/pomerium

What did you see in the logs?

[pomerium.csv](https://github.com/pomerium/pomerium/files/10951226/pomerium.csv)

Additional context

Add any other context about the problem here.

When I use in my compose file

“image: pomerium/pomerium:v0.20.0”

it works ok.

I have been using Pomerium (Synology-docker) since v0.6.x or so and never had had this problem.

Thanks in advance for the attention, please be patient with me because I am not a techy guy. I am good only at following step-by-step instructions.

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 23 (11 by maintainers)

Most upvoted comments

Hello,

Just to report that I tested with v0.22.2 recently released but the same situation.