All Collections
Advanced usage
Using a custom domain with Bugfender
Using a custom domain with Bugfender
Jordi Giménez avatar
Written by Jordi Giménez
Updated over a week ago

Our SDK usually contacts our servers at (or similar, this might be different if you have a private instance). You might be interested in sending the logs using a custom domain, for example This article explains the steps necessary to set this up.


  • A DNS entry on your domain, for example

  • An SSL certificate for that domain name

  • A proxy that redirects the traffic to

Proxying the traffic using a proxy and Let's Encrypt

You can run a small server that does the TLS termination with your domain name and forwards all traffic to our servers. You can do that with your proxy of preference, for example NGINX, Apache, HAProxy or Traefik.

Here is a sample set of configuration files for Traefik with a certificate generated using Let's Encrypt:


address = ":80"
to = "websecure"
scheme = "https"

address = ":443"

email = "[email protected]" #TODO: fill in your email address
storage = "ssl/acme.json"

filename = "traefik_dynamic.toml"


rule = "Host(``)" #TODO: fill in your hostname
entrypoints = ["websecure"]
service = "api"
certResolver = "lets-encrypt"

passHostHeader = false
url = ""

You can run this example with the following command:

docker run -d \
-v $PWD/traefik.toml:/traefik.toml \
-v $PWD/traefik_dynamic.toml:/traefik_dynamic.toml \
-v $PWD/ssl:/ssl \
-p 80:80 -p 443:443 \

Did this answer your question?