Custom domain

5min
Ticketmatic supports custom domains for the ticket sales flows. This allows you to use any domain, including a (sub)domain of the customer, for the web sales pages instead of the default apps.ticketmatic.com. If your own domain is for example www.mycustomdomain.com, you could set up tickets.mycustomdomain.com or shop.mycustomdomain.com for the web sales widgets.
﻿
The set-up of a domain requires technical know-how from your internal IT department. 
Ticketmatic cannot support in the actual implementation of the domain on your side. 
Setting up the custom domain
In order to use a custom domain (tickets.mycustomdomain.com), you need to perform the following steps.
1. Get an ssl certificate for the custom domain
Ticketmatic only allows https traffic, so you need to have a valid ssl certificate for the custom domain and set this up correctly.
2. Setup a proxy on the custom domain to the Ticketmatic servers
You need to setup a proxy on the custom domain that redirects traffic to the Ticketmatic servers. This can be handled easily in the http server. For example for nginx, you can use the following configuration:
nginx
server {
    listen 443 ssl;
    server_name tickets.mycustomdomain.com;

    # Proxy the custom domain to https://apps.ticketmatic.com
    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass https://apps.ticketmatic.com/;
    }
}

# Redirect all http traffic to https
server {
    listen 80;
    server_name tickets.mycustomdomain.com;

    add_header Strict-Transport-Security max-age=15768000;

    rewrite ^(.*)$ https://$host$1 permanent;
}
server {
    listen 443 ssl;
    server_name tickets.mycustomdomain.com;

    # Proxy the custom domain to https://apps.ticketmatic.com
    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass https://apps.ticketmatic.com/;
    }
}

# Redirect all http traffic to https
server {
    listen 80;
    server_name tickets.mycustomdomain.com;

    add_header Strict-Transport-Security max-age=15768000;

    rewrite ^(.*)$ https://$host$1 permanent;
}
﻿
When a user requests a web sales page on the custom domain, the request will be proxied to Ticketmatic and the web sales page will be delivered to the user.
Only the initial request will use the proxy. All subsequent requests for assets and javascript calls to the backend will go directly to the Ticketmatic servers without touching the custom domain. This will keep the load on the custom domain to a minimum.
3. Allow traffic from the custom domain in Ticketmatic
A Ticketmatic account only allows traffic from domains that you explicitely specify:
Go to the Account parameters module in the Settings app
Add the custom domain to the Allowed domains. Make sure to include the protocol:
Allowed domains
﻿
﻿
Ticket sales flows
Authenticated flows