matusnovak/README.md

Matrix

matrix.org chat is split into two parts, the server and the client. The server we are going to use is called Synapse and the client is Riot.im. The Synapse will also need Postgres database and Redis for caching.

0. Folders

Make sure your folder structure looks like this.

example/
  data/
    postgres/
      data/
        (empty)
    traefik/
      (empty)
    matrix/
      nginx/
        (empty)
      synapse/
        (empty)
      riot/
        (empty)
  docker-compose.yml

You can generate them via:

mkdir -p data/postgres/data
mkdir -p data/traefik
mkdir -p data/matrix/{nginx,synapse,riot}
touch docker-compose.yml

1. Traefik

Create your basic Traefik configuration. The following should work out of the box, if you change your email in the ACME section.

# data/traefik/traefik.yml
entryPoints:
  web:
    address: ":80"
  web-secure:
    address: ":443"

api:
  dashboard: true
  insecure: true

providers:
  file:
    directory: "/config"
    watch: true
  docker:
    endpoint: "unix:///var/run/docker.sock"
    network: "example_default"
    watch: true
    exposedByDefault: false

certificatesResolvers:
  letsencrypt:
    acme:
      email: "your_name@example.com"
      storage: "/acme.json"
      httpChallenge:
        entryPoint: "web"

The following additional Traefik config is useful for http to https automatic redirection.

# data/traefik/config/routers.yml
http:
  routers:
    redirecttohttps:
      entryPoints:
        - "web"
      middlewares:
        - "httpsredirect"
      rule: "HostRegexp(`{host:.+}`)"
      service: "noop@internal"

# data/traefik/config/middlewares.yml
http:
  middlewares:
    httpsredirect:
      redirectScheme:
        scheme: https
        permanent: true

2. Postgres

Make sure you have a postgres database with a login for the Synapse server.

The following is a sample docker-compose config for Postgres.

# docker-compose.yml
services:
  traefik:
    ...
  postgres:
    image: "postgres:9.6"
    restart: "unless-stopped"
    environment:
      POSTGRES_PASSWORD: "admin"
    volumes:
      - "./data/postgres/data:/var/lib/postgresql/data"

The following code will create a database synapse with user synapse and password password. Make sure that your database has the correct encoding!

CREATE ROLE synapse;
ALTER ROLE synapse WITH PASSWORD 'password';
ALTER ROLE synapse WITH LOGIN;
CREATE DATABASE synapse ENCODING 'UTF8' LC_COLLATE='C' LC_CTYPE='C' template=template0 OWNER synapse;
GRANT ALL PRIVILEGES ON DATABASE synapse TO synapse;

3. Redis

Make sure you have redis running. Example docker-compose configuration:

# docker-compose.yml
services:
  traefik:
    ...
  postgres:
    ...
  redis:
    image: "redis:latest"
    restart: "unless-stopped"

4. Synapse

Note: You will have two sub-domains for Synapse via Traefik. One matrix.example.com which will be handled by Nginx and a second one synapse.example.com which will point directly into your Synapse server. It will be explained in a later section below.

First create a sample config. This will also create your signing key and bunch of other secrets.

docker run -it --rm \
    -v $(pwd)/data/matrix/synapse:/data \
    -e SYNAPSE_SERVER_NAME=matrix.example.com \
    -e SYNAPSE_REPORT_STATS=yes \
    -e UID=1000 \
    -e GID=1000 \
    matrixdotorg/synapse:latest generate

This will create the following files:

example/
  data/
    ...
    matrix/
      nginx/
        (empty)
      synapse/
        homeserver.yaml
        matrix.example.com.log.config
        matrix.example.com.signing.key
      riot/
        (empty)

Edit the homeserver.yaml so you end up with something like the config below. (notice the enable_registration!)

# data/matrix/synapse/homeserver.yaml
server_name: "matrix.example.com"

pid_file: /data/homeserver.pid

web_client_location: https://riot.example.com/

public_baseurl: https://synapse.example.com/

report_stats: true

enable_registration: true

listeners:
  - port: 8008
    tls: false
    type: http
    x_forwarded: true

    resources:
      - names: [client, federation]
        compress: false

retention:
  enabled: true

federation_ip_range_blacklist:
  - '127.0.0.0/8'
  - '10.0.0.0/8'
  - '172.16.0.0/12'
  - '192.168.0.0/16'
  - '100.64.0.0/10'
  - '169.254.0.0/16'
  - '::1/128'
  - 'fe80::/64'
  - 'fc00::/7'

database:
  name: psycopg2
  args:
    user: synapse
    password: password
    database: synapse
    host: postgres   
    cp_min: 5
    cp_max: 10

log_config: "/data/matrix.example.com.log.config"

media_store_path: "/data/media_store"

registration_shared_secret: "abc"

macaroon_secret_key: "abc"

form_secret: "abc"

signing_key_path: "/data/matrix.example.com.signing.key"

trusted_key_servers:
  - server_name: "matrix.org"

redis:
  enabled: true
  host: redis
  port: 6379

Now add your docker-compose config for Synapse:

# docker-compose.yml
services:
  traefik:
    ...
  postgres:
    ...
  redis:
    ...
  synapse:
    image: "matrixdotorg/synapse:latest"
    restart: "unless-stopped"
    environment:
      SYNAPSE_CONFIG_DIR: "/data"
      SYNAPSE_CONFIG_PATH: "/data/homeserver.yaml"
      UID: "1000"
      GID: "1000"
      TZ: "Europe/London"
    volumes:
      - "./data/matrix/synapse:/data"
    labels:
      - "traefik.enable=true"
      - "traefik.http.services.synapse.loadbalancer.server.port=8008"
      - "traefik.http.routers.synapse.rule=Host(`synapse.example.com`)"
      - "traefik.http.routers.synapse.entrypoints=web-secure"
      - "traefik.http.routers.synapse.tls.certresolver=letsencrypt"

Now when you go to https://synapse.example.com/ you should be redirected to https://synapse.example.com/_matrix/static/ and you should see It works! Synapse is running.

5. Nginx

So the Synapse server is running, but this is not everything you need for federation. You may have noticed that we have used two domains: synapse.example.com and matrix.example.com.

The federation documentation is bit configusing if you don't know enough about how Matrix works internally. Hopefully this example below will explain it.

Create the following files:

The Nginx configuration file at data/matrix/nginx/matrix.conf relative to your docker-compose.yml with the following contents:

server {
  listen         80 default_server;
  server_name    matrix.example.com;

 # Traefik -> nginx -> synapse
 location /_matrix {
    proxy_pass http://synapse:8008;
    proxy_set_header X-Forwarded-For $remote_addr;
    client_max_body_size 128m;
  }

  location /.well-known/matrix/ {
    root /var/www/;
    default_type application/json;
    add_header Access-Control-Allow-Origin  *;
  }
}

The data/matrix/nginx/www/.well-known/matrix/client with the following contents:

{
  "m.homeserver": {
    "base_url": "https://matrix.example.com"
  }
}

And the data/matrix/nginx/www/.well-known/matrix/server with the following contents:

{
  "m.server": "synapse.example.com:443"
}

And the docker-compose config for Nginx:

# docker-compose.yml
services:
  traefik:
    ...
  postgres:
    ...
  redis:
    ...
  synapse:
    ...
  nginx:
    image: "nginx:latest"
    restart: "unless-stopped"
    volumes:
      - "./data/matrix/nginx/matrix.conf:/etc/nginx/conf.d/matrix.conf"
      - ./data/matrix/nginx/www:/var/www/
    labels:
      - "traefik.enable=true"
      - "traefik.http.services.matrix.loadbalancer.server.port=80"
      - "traefik.http.routers.matrix.rule=Host(`matrix.example.com`)"
      - "traefik.http.routers.matrix.entrypoints=web-secure"
      - "traefik.http.routers.matrix.tls.certresolver=letsencrypt"

After you start the container, you should be able to access https://matrix.example.com/.well-known/matrix/client which gives you "base_url": "https://matrix.example.com".

And also you should be able to access https://matrix.example.com/.well-known/matrix/server which gives you "m.server": "synapse.example.com:443".

And also accessing https://matrix.example.com/_matrix/static/ should show you the exact same page as shown at https://synapse.example.com/_matrix/static/.

The Nginx simply acts as a proxy in this case, with two additional files.

6. Federation tester

Now, when you go to https://federationtester.matrix.org/ and type in your domain name, in this case matrix.example.com (without https) you should get all green checks.

7. Riot Web UI

The last thing is to set up the Riot Web UI which will be used to send the messages.

Create a new file at data/matrix/riot/config.json with the following contents:

{
  "default_server_config": {
    "m.homeserver": {
      "base_url": "https://matrix.example.com",
      "server_name": "matrix.example.com"
    },
    "m.identity_server": {
      "base_url": "https://vector.im"
    }
  },
  "disable_custom_urls": false,
  "disable_guests": false,
  "disable_login_language_selector": false,
  "disable_3pid_login": false,
  "brand": "Element",
  "integrations_ui_url": "https://scalar.vector.im/",
  "integrations_rest_url": "https://scalar.vector.im/api",
  "integrations_widgets_urls": [
    "https://scalar.vector.im/_matrix/integrations/v1",
    "https://scalar.vector.im/api",
    "https://scalar-staging.vector.im/_matrix/integrations/v1",
    "https://scalar-staging.vector.im/api",
    "https://scalar-staging.riot.im/scalar/api"
  ],
  "bug_report_endpoint_url": "https://riot.im/bugreports/submit",
  "defaultCountryCode": "GB",
  "showLabsSettings": false,
  "features": {
    "feature_new_spinner": "labs",
    "feature_pinning": "labs",
    "feature_custom_status": "labs",
    "feature_custom_tags": "labs",
    "feature_state_counters": "labs"
  },
  "default_federate": true,
  "default_theme": "light",
  "roomDirectory": {
    "servers": [
      "matrix.org"
    ]
  },
  "welcomeUserId": "@riot-bot:matrix.org",
  "piwik": {
    "url": "https://piwik.riot.im/",
    "whitelistedHSUrls": [
      "https://matrix.org"
    ],
    "whitelistedISUrls": [
      "https://vector.im",
      "https://matrix.org"
    ],
    "siteId": 1
  },
  "enable_presence_by_hs_url": {
    "https://matrix.org": false,
    "https://matrix-client.matrix.org": false
  },
  "settingDefaults": {
    "breadcrumbs": true
  },
  "jitsi": {
    "preferredDomain": "jitsi.riot.im"
  }
}

And add Riot to your docker-compose file:

# docker-compose.yml
services:
  traefik:
    ...
  postgres:
    ...
  redis:
    ...
  synapse:
    ...
  nginx:
    ...
  riot:
    image: "bubuntux/riot-web:latest"
    volumes:
      - "./data/matrix/riot/config.json:/etc/riot-web/config.json:ro"
    labels:
      - "traefik.enable=true"
      - "traefik.http.services.riot.loadbalancer.server.port=80"
      - "traefik.http.routers.riot.rule=Host(`riot.example.com`)"
      - "traefik.http.routers.riot.entrypoints=web-secure"
      - "traefik.http.routers.riot.tls.certresolver=letsencrypt"

8. Logging in

Go to https://riot.example.com and click register and select "Advanced" and enter the Homeserver URL as https://matrix.example.com (NOT https://synapse.example.com!).

After creating an account, simply log in. That's it.

9. Testing federation by joinin public room

Navigate to https://riot.example.com/#/room/#hello-matrix:matrix.org This will join you to #hello-matrix:matrix.org room on <matrix.org>.

If you get 401 unauthorized error in your logs (Synapse logs), check the SVR DNS record below.

10. SVR DNS record

Note: This may not be needed!

Add the following SVR record to your DNS server:

_matrix._tcp.matrix.synapse.example.com

With value of:

1 10 443 synapse.example.com

After it is done, you should be able to test if it is correct via dig or similar CLI tool:

dig -t SRV _matrix._tcp.matrix.example.com @8.8.8.8

And should print the following:

;; ANSWER SECTION:
_matrix._tcp.matrix.example.com. 299 IN SRV 1 10 443 synapse.example.com.

Optional OpenLDAP

It is possible to integrate Synapse with OpenLDAP. In this case you don't need to create any user from the Riot Web UI. All authentication will be handled by OpenLDAP server.

Add this into your homeserver.yml file:

password_providers:
  - module: "ldap_auth_provider.LdapAuthProvider"
    config:
      enabled: true
      uri: "ldap://openldap:389"
      start_tls: false
      base: "ou=users,dc=example,dc=com"
      attributes:
         uid: "uid"
         mail: "email"
         name: "cn"
      bind_dn: cn=admin,dc=example,dc=com
      bind_password: password
      filter: "(memberOf=cn=matrix,ou=groups,dc=example,dc=com)"

Assuming that:

Your OpenLDAP server can be accessed via Docker network at openldap:389.
You have domain of dc=example,dc=com.
You have admin (or any user for bind) cn=admin,dc=example,dc=com.
You have an organization unit of users at ou=users,dc=example,dc=com.
You have a groupOfUniqueNames as cn=matrix,ou=example,dc=example,dc=com.
Your users are added into the group cn=matrix so they have a property memberOf.

I recommend using OpenLDAP as the following:

services:
  openldap:
    image: "osixia/openldap:latest"
    restart: "unless-stopped"
    environment:
      LDAP_ORGANISATION: "Homelab"
      LDAP_DOMAIN: "dc=example,dc=com"
      LDAP_ADMIN_PASSWORD: "password"
      LDAP_REMOVE_CONFIG_AFTER_SETUP: "false"
    volumes:
      - "./data/ldap/data:/var/lib/ldap"
      - "./data/ldap/config:/etc/ldap/slapd.d"

The end

In the end, your files should look like this:

example/
  data/
    postgres/
      data/
        ... stuff ...
    traefik/
      config/
        middlewares.yml
        routers.yml
      traefik.yml
      acme.json
    matrix/
      nginx/
        www/
          .well-known/
            matrix/
              server
              client
        matrix.conf
      synapse/
        media_store/
          ... stuff ...
        homeserver.yml
        matrix.example.com.log.config
        matrix.example.com.signing.key
      riot/
        config.json
  docker-compose.yml

matusnovak · 2021-02-09T19:37:57Z

@TekExplorer

What happens when you do not use a subdomain? Also, do you mean telling users to use a subdomain for Riot Web?

matusnovak · 2021-02-09T19:38:00Z

@majso

Done, it's the optional last section. It's the exact setup I use myself and works without an issue.

TekExplorer · 2021-02-10T03:10:08Z

@matusnovak
it seems to sort of work. i cant add an email with the following error: request failed: CORS request rejected: https://<redacted_domain>.com/_matrix/client/r0/account/3pid/email/requestToken and adding a phone number doesn't work? I'm not sure how to correct that.

and yeah, for riot web, and for users to be @user:domain.com instead of @user:matrix.domain.com

edit: looking at the network tab in my browser, looks to actually be a 504 gateway timeout 🤔
edit2: and the response is CORS Missing Allow Origin

TekExplorer · 2021-02-10T03:48:48Z

also, is the synapse subdomain even needed? whats it used for?

matusnovak · 2021-02-11T19:19:43Z

@TekExplorer

The synapse domain is needed for the SVR DNS record. I am not 100% sure this is really required by Synapse. I got only confusing answers when searching for that on Matrix forums. I would advise to ask someone from the Matrix team to confirm this.

That CORS error sounds to me that it is expecting a different domain based on the configuration. Seems like the issue is due to this: matrix-org/synapse#1595 That CORS is triggered from your browser, from Riot trying to contact Synapse when you are adding a user, right?

What are the CORS headers sent back to you from Synapse? Mine look like this:

access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept, Authorization, Date
access-control-allow-methods: GET, HEAD, POST, PUT, DELETE, OPTIONS
access-control-allow-origin: *

Have you modified the domain you want your users to access after you have set up the synapse configuration? (First part of the step 4. from above). If yes, this is a big no-no. You can't modify your domain after you have run that generate command.

About the 504 gateway timeout, this may be due to misconfigured Traefik, labels in the Docker Compose, or misconfigured Nginx. I would double check that all of the Docker containers are on the same network (it should be your_stack_name + _default). It is possible you may have encountered the same issue as BOZG in here. You may need to add traefik.docker.network label to your containers. All of this is just a theory, this really depends on how have you set it up and what have you changed.

If it helps in any way, here is Synapse+Nginx+Riot+Coturn docker-compose config all in one place: https://github.com/matusnovak/homelab/blob/master/docker-compose.matrix.yml

urtzai · 2021-03-02T16:29:51Z

Hi! I think is the most complete guide I found so far, but could you please write some example of the Traefik docker-compose.yml section? Thank you!!

matusnovak · 2021-03-04T21:31:42Z

@urtzai

Whoops, that should have been there. I have updated the guide. Thank you for letting me know.

RealAkito · 2021-05-18T14:17:50Z

Good stuff man, thanks!

jacktheripper19 · 2021-06-11T10:04:45Z

Hi! is there anyway to disable the access to the static page in https://synapse.example.com/_matrix/static/ while keeping the federation ?

kleo · 2021-11-28T16:11:19Z

Here's the format for coturn postgres

psql-userdb="host=postgres dbname=turn user=turn password=password connect_timeout=30"

And add this to docker-entrypoint-initdb.d on your postgres volumes https://github.com/coturn/coturn/blob/master/docker/postgresql/schema.sql

And init.sql

CREATE ROLE turn;
ALTER ROLE turn WITH PASSWORD 'password';
ALTER ROLE turn WITH LOGIN;
CREATE DATABASE turn OWNER turn;
GRANT ALL PRIVILEGES ON DATABASE turn TO turn;

docker-compose.yml

[...]
  postgres:
    image: postgres:11
    restart: unless-stopped
    environment:
      POSTGRES_PASSWORD: "password"
    volumes:
      - ./data/postgres/data:/var/lib/postgresql/data
      - ./data/postgres/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
[...]

ref: https://github.com/coturn/coturn/blob/master/INSTALL#L868

ivvil · 2021-12-01T18:28:25Z

Thanks for the how to, I'm trying to set this up myself, but could someone explain what are you supposed to do with the Traefik docker config? I'm new to docker.

abyssmemes · 2021-12-26T18:12:53Z

Thanks for guide! Well may i can do this without traefik? Just with Ngnix reverse proxy?

TekExplorer · 2021-12-26T18:19:18Z

I don't see why not. Take inspiration from this guide, and perhaps the official docker-compose files in the main ptero repos to design your setup

…

On Sun, Dec 26, 2021, 1:13 PM Eduard Lugovtsov ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Thanks for guide! Well may i can do this without traefik? Just with Ngnix reverse proxy? — Reply to this email directly, view it on GitHub <https://gist.github.com/37109e60abe79f4b59fc9fbda10896da#gistcomment-4008303>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHHDKZUPZENFJ5DKJ7O6HIDUS5LLDANCNFSM4WQWNFAQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

anoadragon453 · 2021-12-26T20:11:49Z

Note that the vectorim/riot-web docker image has been replaced by vectorim/element-web. The former no longer receives updates.

pnposch · 2022-01-05T13:02:07Z

@abyssmemes Not sure if that helps, but i used the nginx-acme-companion instead of traefik, see my fork for the details.

psycho0verload · 2022-01-14T04:52:55Z

@matusnovak
Thank you for the detailed tutorial. Does the integration server work for you. I have now worked through various tutorials but I always get an error that the integration server is not available when I want to use a sticker, for example.

sethforprivacy · 2022-02-07T16:25:38Z

One correction here -- if you do not set the Traefik ports to be exposed using host mode, the X-Forwarded-For IP will be incorrect and will cause issues with Synapse down the line, especially around federation.

The ports should be specified like:

      - target: 80
        published: 80
        mode: host
      - target: 443
        published: 443
        mode: host

C4tWithShell · 2022-09-02T12:36:36Z

Hi. Thanks for guide! Can coturn be configured with traefik labels?

Cheety · 2023-03-02T18:00:45Z

If you get 502 Error try to add / at the end of location /_matrix:

 # Traefik -> nginx -> synapse
 location /_matrix/ {
    proxy_pass http://synapse:8008;
    proxy_set_header X-Forwarded-For $remote_addr;
    client_max_body_size 128m;
  }

trackmastersteve · 2024-01-02T01:35:10Z

I am having issues with Traefik using "traefik default cert" instead of generating the correct certs for my domain name. What am I doing wrong?

EDIT: I think I found the issue. The Traefik log shows "...uses non-exsistent resolver: letsencrypt" for each of the sub-domains.

matusnovak · 2024-01-02T06:01:56Z

I am having issues with Traefik using "traefik default cert" instead of generating the correct certs for my domain name. What am I doing wrong?

EDIT: I think I found the issue. The Traefik log shows "...uses non-exsistent resolver: letsencrypt" for each of the sub-domains.

Yup, that would be it.

Btw, just to note, for HTTP 404 paths (anything that does not belong to Matrix) will give you the traefik default cert.

melroy89 · 2024-10-02T10:55:14Z

The official docs don't mention Redis anymore: https://github.com/element-hq/synapse/blob/develop/contrib/docker/docker-compose.yml ? It seems not be required or used anymore!?

Also the word "Redis" isn't mentioned here: https://hub.docker.com/r/matrixdotorg/synapse

L0giXX · 2024-10-08T12:53:36Z

Quick question, do I need to own a public domain to make this setup work correctly, e.g internal federation between two matrix synapse servers?

OptimusGREEN · 2024-11-09T20:50:58Z

The federation checker is failing for me
Get "https://x.x.x.x:8448/_matrix/key/v2/server": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I don't see port 8448 mentioned in this post?

matusnovak · 2024-11-14T22:40:26Z

The official docs don't mention Redis anymore: https://github.com/element-hq/synapse/blob/develop/contrib/docker/docker-compose.yml ? It seems not be required or used anymore!?

@melroy89 This guide may be outdated by now. Sorry, I do not have the free time to update it.

Quick question, do I need to own a public domain to make this setup work correctly, e.g internal federation between two matrix synapse servers?

@L0giXX I don't think so, but you should still assign some internal local DNS record for your servers.

I don't see port 8448 mentioned in this post?

@OptimusGREEN That looks like the default HTTPS port set by the Traefik. Double check that the ports are correctly set.

PedanXr · 2025-03-14T11:16:33Z

@OptimusGREEN Did you manage to make it work? Running into the same issue with federation tester

udo-hase · 2025-03-14T16:07:42Z

Hey @matusnovak ,
thanks a lot for your description. With some traefik modifikations i was able to setup my own matrix server including federation with your documentation!
Great work and many thanks!!!!

OptimusGREEN · 2025-03-15T18:10:21Z

@OptimusGREEN Did you manage to make it work? Running into the same issue with federation tester

I did but stopped using it now so can't check what the issue was but I think i was using the wrong fqdn either on the front end or back end or something silly like that. sorry I can't be any more help

eiabea · 2026-01-20T11:43:38Z

Awesome setup, thank you!

Unfortunately I'm having issues joining public rooms. It looks like traefik is sanitizing the join request path. https://federationtester.matrix.org/ returns only successful results

curl -vL 'https://matrix.example.com/_matrix/client/v3/join/%23dev%3Anymtech.chat'

results in an instant 400-response from traefik and never reaches the synapse server

traefik-1  | x.x.x.x - - [20/Jan/2026:11:39:01 +0000] "POST /_matrix/client/v3/join/%23dev%3Anymtech.chat HTTP/2.0" 400 0 "-" "-" 149 "matrix-nginx@docker" "-" 0ms

Testing it with a plain room string

curl -vL 'https://matrix.example.com/_matrix/client/v3/join/nymtech.chat'

gives me a response from the synapse server

{"errcode":"M_UNKNOWN","error":"nymtech.chat was not legal room ID or room alias"}

I spend way to long looking for a solution for this, hope someone can give me a hint 🙏

eiabea · 2026-01-20T11:56:01Z

I fixed it! After rolling back all changes and digging through some example configs again I got it to work by disabling x_forwarded 🥳

homeserver.yaml

listeners:
  - port: 8008
    tls: false
    type: http
    x_forwarded: false
    resources:
      - names: [client, federation]
        compress: false

matusnovak/README.md

Matrix

0. Folders

1. Traefik

2. Postgres

3. Redis

4. Synapse

5. Nginx

6. Federation tester

7. Riot Web UI

8. Logging in

9. Testing federation by joinin public room

10. SVR DNS record

Optional OpenLDAP

The end

matusnovak commented Feb 9, 2021

Uh oh!

matusnovak commented Feb 9, 2021

Uh oh!

TekExplorer commented Feb 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

TekExplorer commented Feb 10, 2021

Uh oh!

matusnovak commented Feb 11, 2021

Uh oh!

urtzai commented Mar 2, 2021

Uh oh!

matusnovak commented Mar 4, 2021

Uh oh!

RealAkito commented May 18, 2021

Uh oh!

jacktheripper19 commented Jun 11, 2021

Uh oh!

kleo commented Nov 28, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ivvil commented Dec 1, 2021

Uh oh!

abyssmemes commented Dec 26, 2021

Uh oh!

TekExplorer commented Dec 26, 2021 via email

Uh oh!

anoadragon453 commented Dec 26, 2021

Uh oh!

pnposch commented Jan 5, 2022

Uh oh!

psycho0verload commented Jan 14, 2022

Uh oh!

sethforprivacy commented Feb 7, 2022

Uh oh!

C4tWithShell commented Sep 2, 2022

Uh oh!

Cheety commented Mar 2, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trackmastersteve commented Jan 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

matusnovak commented Jan 2, 2024

Uh oh!

melroy89 commented Oct 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

L0giXX commented Oct 8, 2024

Uh oh!

OptimusGREEN commented Nov 9, 2024

Uh oh!

matusnovak commented Nov 14, 2024

Uh oh!

PedanXr commented Mar 14, 2025

Uh oh!

udo-hase commented Mar 14, 2025

Uh oh!

OptimusGREEN commented Mar 15, 2025

Uh oh!

eiabea commented Jan 20, 2026

Uh oh!

eiabea commented Jan 20, 2026

Uh oh!

TekExplorer commented Feb 10, 2021 •

edited

Loading

kleo commented Nov 28, 2021 •

edited

Loading

Cheety commented Mar 2, 2023 •

edited

Loading

trackmastersteve commented Jan 2, 2024 •

edited

Loading

melroy89 commented Oct 2, 2024 •

edited

Loading