> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/getting-started/setup/url-and-ssl-certificate.md).

# URL & SSL Certificate

**URL & SSL** is the fourth step of the wizard, where you set the address WriteBackExtreme serves on. Tableau only loads extensions over HTTPS, so an SSL certificate is required somewhere in the chain: either on WriteBackExtreme itself, or on the proxy in front of it.

There are 2 possible setups:

* [The application is running behind a reverse-proxy or load-balancer](#configured-behind-reverse-proxyload-balancer)
* [The application is exposed to the internet](#configured-with-direct-access-from-the-internet)

### Configured with direct access from the Internet

This indicates that the machine is **not** running behind a reverse proxy or load balancer.

Only use this setup if the server is **directly exposed to the internet**.

**Configuration Example:**

| Field               | Value                            |
| ------------------- | -------------------------------- |
| **Domain**          | `wbe.yourdomain.com` *(no path)* |
| **Port**            | `443`                            |
| **SSL Certificate** | Upload a full-chain certificate  |

**Port** defaults to `8080`, and changes to `443` as soon as you upload a certificate. Make sure the port is not already in use; the wizard warns you when something else is listening on it, and the application fails to start on a port conflict. A few ports are blocked outright, and the wizard then says **The port number is restricted. Please select a different port**.

{% hint style="info" %}
The protocol (e.g. `http://` or `https://`) should be omitted in the domain field.
{% endhint %}

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-039956d107c7baa578a859eaab01251fa1084a78%2Fimage%20(35).png?alt=media" alt=""><figcaption></figcaption></figure>

### Configured behind Reverse Proxy/Load Balancer

When the machine where WriteBackExtreme is going to be installed is not directly accessible from outside and has a load balancer or reverse proxy that redirects the incoming traffic from the domain to this machine, tick **Application is running behind a proxy or load balancer**. The message at the top of the step shows the URL the application will be reachable on, which is how you configure the proxy.

Ticking the option renames the first field to **Hostname** — the name of this machine, used to validate the certificate you upload — and adds the external **Domain** and **External Port** of the proxy. Tick **Proxy/load balancer has SSL certificate configured.** when the proxy terminates SSL, and you do not need to upload a certificate here at all.

**Configuration Example:**

| Field               | Value                                               |
| ------------------- | --------------------------------------------------- |
| **Hostname**        | `localhost`                                         |
| **Port**            | `8080` (or your internal port)                      |
| **Domain**          | `wbe.yourdomain.com` *(no path)*                    |
| **External Port**   | `443` (`80` without SSL)                            |
| **SSL Certificate** | Upload a full-chain certificate (.crt/.key or .pfx) |

> **Do not include a path (like `/backend or /extension`) in the domain field. Only the domain is valid here.**

{% hint style="info" %}
The protocol (e.g. `http://` or `https://`) should be omitted in the domain and hostname field.
{% endhint %}

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-acd33bfb90ad6c98d89d71be05a3c1324ab22b0d%2Fimage%20(36).png?alt=media" alt=""><figcaption></figcaption></figure>

### Uploading a certificate

The **SSL Certificate** upload area accepts `.crt`, `.cer`, `.cert`, `.key`, `.pfx` and `.p12` files. Upload either a `.pfx`/`.p12` bundle, with its **Passphrase** if it has one, or both a `.crt` and a `.key` file — upload one without the other and the wizard tells you which is missing. The certificate needs to be a **full-chain** certificate, and the key may not be encrypted.

Once a certificate is installed, the step shows a **Current installed certificate** box with its expiry date and valid domains, and a **Remove Certificates** button.

The protocol (`http://` or `https://`) is left out of the domain and hostname fields, and so is any path.

### Troubleshooting SSL certificates

Sometimes the application does not like the provided ssl certificates. These error could occur:

<details>

<summary>Failed to decode PEM block containing private key</summary>

1. Open keyfile and check if it starts with -----BEGIN PRIVATE KEY-----

If there is something above this line, delete it. (Same applies to certificates!)

2. Open your keyfile and check if it is encrypted. (Encrypted private keys start with -----BEGIN ENCRYPTED PRIVATE KEY-----) When it is encrypted, you need to decrypt it. You can do that via openssl (if installed on your machine) in your terminal using the following command:

`openssl rsa -in <encrypted_private.key> -out <decrypted_private.key>`

</details>

<details>

<summary>Could not unpackage pfx/p12 file - pkcs12: expected exactly two safe bags in the PFX</summary>

The PFX file does not have the correct format. The best way is to convert pfx into a .crt and .key file. You can do this via openssl when this is installed on your system:

```
## extract the key from the pfx file
openssl pkcs12 -in [yourfile.pfx] -nocerts -out certificate.key

## extract the certificate from the pfx file
openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out certificate.crt

## Decrypt the keyfile
openssl rsa -in certificate.key -out certificate-decrypted.key

# Upload the certificate-decrypted.key and certificate.crt to writeback. 
```

</details>

<details>

<summary>Certificate does not match domain/IP</summary>

If you are using an IP address instead of a domain name, make sure the certificate includes the IP in the **Subject Alternative Name (SAN)** field.

* Example for OpenSSL:

  ```bash
  -addext "subjectAltName=IP:12.0.19.89"
  ```

  (Use `IP:` instead of `DNS:` when adding an IP address).
* Example for OpenSSL:

  ```bash
  -addext "subjectAltName=DSN:yourhostname"
  ```

  (Use `DNS:` when adding a Domain).

**Important:**

* If you change the certificate creation string, you must also regenerate both the `.crt` **and** the `.key` files and update them in the Management Console. Using a mismatched `.crt` and `.key` will cause errors.

</details>

#### Server startup problems

<details>

<summary>Could not startup server, Contact Apps For Tableau support when the problem persists</summary>

The app server is unable to start. This can have multiple causes like:

* Application is configured as administrator but is currently not running with administrator previleges.
* Check if there is no other WriteBackExtreme proces running in the background. Open Task manager and select the `Details` tab. You should have only one process called WriteBackExtreme.
* Check if there is no other process running on the port that is configured in WriteBackExtreme. You can do that with this command in cmd:

```
netstat -aon
```

* Check is the application log. This log file is located at \<path>/.wbe-runtime/storage/logs/wbe-application.log
* Open powershell and navigate to the directory where WriteBackExtreme.exe is located. run this command to manually trigger the application server:

```
./WriteBackExtreme.exe serve
```

This command might give more details about what went wrong.

</details>

<details>

<summary>listen tcp :443: bind: Only one usage of each socket address (protocol/network address/port) is hormally permitted</summary>

When this error appears in your wbe-application.log it is not able to spin the server because the port you have configured is already in use by another program.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/getting-started/setup/url-and-ssl-certificate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
