Nicolas Steinmetz

@rbcolom take care about your environment variables - you should not have quotes - cf https://docs.docker.com/compose/compose-file/#environment For my wallabag docker-compose.yml: ``` version: '2' services: wallabag: image: wallabag/wallabag environment: - POSTGRES_USER=postgres...

if you use a traefik docker image, you need to connect traefik to your wallabag network (or the opposite). I use the android version without any issue.

Hey, Glad to learn here that this "issue" is fixed soon https://github.com/luxas/kubernetes-on-arm/issues/1 :) As said on blog post, happy to contribute with at least testing and reporting issues. My 2...

Hi @rokroskar, I have the same issue, did you find a way to get it working ? Thanks! I opened also https://gitlab.com/gitlab-org/gitlab/issues/208825

Seems the bug changed a bit since yours in fact. Seems now the `/v2/tokens` is added automatically so I can't use a V3 endpoint whereas OVH (my openstack provider) will...

@rokroskar I tried indeed but forgot to mention it - and it fails too. It leads to `path => "/v3/v2.0/tokens"`

Hi @axi I switched to S3 endpoints on OVH instead of swift for the time being. The issue on gitlab side is in backlog but no progress for a month.

@ShamoX thanks for the tip ! This works like a charm: ```ruby gitlab_rails['backup_upload_connection'] = { 'provider' => 'OpenStack', 'openstack_username' => 'XXX', 'openstack_api_key' => 'XXX', 'openstack_auth_url' => 'https://auth.cloud.ovh.net', 'openstack_region' => 'XXX'...

@achevalet it seems indeed that v3 endpoints are not available in your case based on what you provide. You should use a V2 auth schema then.

So contact your provider for more info about this I would say :)