diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md index 3db8175d3..d078f2a19 100644 --- a/docs/configuring-well-known.md +++ b/docs/configuring-well-known.md @@ -191,8 +191,8 @@ Make sure to: No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs: -- `https:///.well-known/matrix/server` -- `https:///.well-known/matrix/client` -- `https:///.well-known/matrix/support` +- `https://example.com/.well-known/matrix/server` +- `https://example.com/.well-known/matrix/client` +- `https://example.com/.well-known/matrix/support` You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md). diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md index d4386fb04..5644ff089 100644 --- a/docs/howto-server-delegation.md +++ b/docs/howto-server-delegation.md @@ -24,7 +24,7 @@ Server Delegation by means of a `/.well-known/matrix/server` file is the most st - you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md). -- any downtime on the base domain (`example.com`) or network trouble between the matrix subdomain (`matrix.example.com`) and the base `` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery): +- any downtime on the base domain (`example.com`) or network trouble between the matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery): > Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures. diff --git a/docs/registering-users.md b/docs/registering-users.md index d725e8486..75863e26b 100644 --- a/docs/registering-users.md +++ b/docs/registering-users.md @@ -36,7 +36,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=` is just a plain username (like `john`), not your full `@:example.com` identifier. -**You can then log in with that user** via the Element service that this playbook has created for you at a URL like this: `https://element./`. +**You can then log in with that user** via the Element service that this playbook has created for you at a URL like this: `https://element.example.com/`. ----- diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md index bfa74ce44..1785a67ca 100644 --- a/docs/updating-users-passwords.md +++ b/docs/updating-users-passwords.md @@ -10,7 +10,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=` is just a plain username (like `john`), not your full `@:example.com` identifier. -**You can then log in with that user** via the Element service that this playbook has created for you at a URL like this: `https://element./`. +**You can then log in with that user** via the Element service that this playbook has created for you at a URL like this: `https://element.example.com/`. ## Option 2 (if you are using an external Postgres server):