# Traefik docker JIRA issue (base url not valid)

**URL:** <https://community.traefik.io/t/traefik-docker-jira-issue-base-url-not-valid/842>\
**Category:** Traefik v1\
**Tags:** docker\
**Created:** [July 9, 2019, 10:19pm UTC](https://community.traefik.io/t/traefik-docker-jira-issue-base-url-not-valid/842 "2019-07-09T22:19:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![G76S](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@G76S](https://community.traefik.io/u/G76S)\
**Post date:** [July 9, 2019, 10:19pm UTC](https://community.traefik.io/t/traefik-docker-jira-issue-base-url-not-valid/842/1 "2019-07-09T22:19:21Z")

</div>

Hi all,

I have a kind of issue here.  
Wanted to install JIRA and Confluence as a docker image, and as a reverse proxy I wanted to use traefik.

After a little try and error and a lot of reading on the traefik site I got the containers running.  
My JIRA and Confluence answers on the subdomains I set up, and I can see the startpages of both.  
So far so good, problem is, when I enter the JIRA setup page it asks for the base URL of the installation. When I enter my subdomain, the validation says the URL is not valid.  
If I log in on the computer where the docker containers are running and use the backend addresses traefik created, then it works.  
So I am guessing it is an iptables/routing/DNS problem, but I am stuck here. Please help.

This is my docker-compose.yml file:

```auto
version: '3.5'

services:
  reverse-proxy:
    restart: always
    networks:
      - web
    image: traefik # The official Traefik docker image
    command: --api --docker # Enables the web UI and tells Traefik to listen to docker
    ports:
      - "80:80" # The HTTP port
      - "8080:8080" # The Web UI (enabled by --api)
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
 
  jira:
    depends_on:
      - pgsql_jira
    restart: always
    image: teamatldocker/jira
    networks:
      - web      
    volumes:
      - jiradata:/var/atlassian/jira
    environment:
      - 'JIRA_DATABASE_URL=postgresql://jira@pgsql_jira/jiradb'
      - 'JIRA_DB_PASSWORD=xxxx'
      - 'SETENV_JVM_MINIMUM_MEMORY=2048m'
      - 'JIRA_PROXY_NAME='
      - 'JIRA_PROXY_PORT='
      - 'JIRA_PROXY_SCHEME='
    logging:
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "50"
    labels:
       - "traefik.frontend.rule=Host:jira.kub-01"
    

  confluence:
    depends_on:
      - pgsql_confluence
    image: teamatldocker/confluence
    networks:
      - web
    volumes:
      - confluencedata:/var/atlassian/confluence
    environment:
      - 'CONFLUENCE_DATABASE_URL=postgresql://confluence@pgsql_confluence/confluencedb'
      - 'CONFLUENCE_DB_PASSWORD=xxxx'
      - 'SETENV_JVM_MINIMUM_MEMORY=2048m'
      - 'CONFLUENCE_PROXY_NAME='
      - 'CONFLUENCE_PROXY_PORT='
      - 'CONFLUENCE_PROXY_SCHEME='
    logging:
      # limit logs retained on host to 25MB
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "50"
    labels:
       - "traefik.frontend.rule=Host:confluence.kub-01"
       
       
  pgsql_jira:
    image: postgres:9.5-alpine
    networks:
      - web
    volumes:
      - postgresqldata:/var/lib/postgresql/data
    environment:
      - 'POSTGRES_USER=jira'
      # CHANGE THE PASSWORD!
      - 'POSTGRES_PASSWORD=xxxx'
      - 'POSTGRES_DB=jiradb'
      - 'POSTGRES_ENCODING=UNICODE'
      - 'POSTGRES_COLLATE=C'
      - 'POSTGRES_COLLATE_TYPE=C'
    logging:
      # limit logs retained on host to 25MB
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "50"
    labels:
      - "traefik.enable=false"

  pgsql_confluence:
    image: postgres:9.5-alpine
    networks:
      - web
    volumes:
      - pgsqldata:/var/lib/postgresql/data
    environment:
      - 'POSTGRES_USER=confluence'
      # CHANGE THE PASSWORD!
      - 'POSTGRES_PASSWORD=xxxx'
      - 'POSTGRES_DB=confluencedb'
      - 'POSTGRES_ENCODING=UNICODE'
      - 'POSTGRES_COLLATE=C'
      - 'POSTGRES_COLLATE_TYPE=C'
    logging:
      # limit logs retained on host to 25MB
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "50"
    labels: 
      - "traefik.enable=false"

volumes:
  jiradata:
    external: false
  confluencedata:
    external: false
  pgsqldata:
    external: false
  postgresqldata:
    external: false

networks:
  web:
    external: true

```

---

<div class="post-metadata">

**Author:** ![daniel.tomcej](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/daniel.tomcej/32/262_2.png) [@daniel.tomcej](https://community.traefik.io/u/daniel.tomcej)\
**Post date:** [July 10, 2019, 2:54am UTC](https://community.traefik.io/t/traefik-docker-jira-issue-base-url-not-valid/842/2 "2019-07-10T02:54:05Z")

</div>

Hello @G76S,

From the documentation at:

[Proxying Atlassian server applications with Apache HTTP Server (mod\_proxy\_http) | Atlassian Support | Atlassian Documentation](https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html)

> Atlassian applications allow the use of reverse-proxies with our products,  
> however Atlassian Support does not provide assistance for configuring them.  
> Consequently, Atlassian cannot guarantee providing any support for them.

Also of note: you are not using an official Atlassian image, you are using a 3rd party image.

There is not much we can assist with, due to the customization, and the non-support from the source.

I would reach out to the teamatldocker group at [GitHub - teamatldocker/jira: Dockerized Atlassian Jira](https://github.com/teamatldocker/jira), as they may be able to provide more assistance.

---

<div class="post-metadata">

**Author:** ![G76S](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@G76S](https://community.traefik.io/u/G76S)\
**Post date:** [July 10, 2019, 7:38am UTC](https://community.traefik.io/t/traefik-docker-jira-issue-base-url-not-valid/842/3 "2019-07-10T07:38:36Z")

</div>

Hi @daniel.tomcej,

thanks for the quick answer.  
I will try to reach to the teamatldocker group. If I got some news, I will drop that here, too, just for documentation.