From 9135d1e1793075a3675834feb2f9c7507651efc2 Mon Sep 17 00:00:00 2001 From: Joshua Goins Date: Tue, 17 Jun 2025 17:08:56 -0400 Subject: [PATCH] Add back hosts editing information to the USAGE guide This was initially removed because the localhost TLD Caddy magic, but I just discovered that this isn't honored by WinHTTP which breaks the retail patcher. So users will still - unfortunately - have to do this. --- USAGE.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/USAGE.md b/USAGE.md index 087f056..8be5b77 100644 --- a/USAGE.md +++ b/USAGE.md @@ -62,6 +62,22 @@ caddy run --config resources/Caddyfile This Caddyfile hosts several domains required for normal operation, for example `ffxiv.localhost` on port 80. If you get a "permission denied" error starting Caddy, you must either start Caddy with elevated privileges (`sudo`) or set the `CAP_NET_BIND_SERVICE` capability. See [here](https://caddyserver.com/docs/quick-starts/caddyfile) for more information on how to do this. +You'll notice that your browser can connect to the `.localhost` sites without any additional configuration, e.g. `ffxiv.localhost`. Whatever magic Caddy does to make this happen _only works in browsers_, so the WinHTTP-based code in FFXIV will fail. To work around this, you will have to edit your hosts file: + +``` +127.0.0.1 admin.ffxiv.localhost +127.0.0.1 ffxiv.localhost +127.0.0.1 launcher.ffxiv.localhost +127.0.0.1 config-dl.ffxiv.localhost +127.0.0.1 frontier.ffxiv.localhost +127.0.0.1 patch-bootver.ffxiv.localhost +127.0.0.1 patch-gamever.ffxiv.localhost +127.0.0.1 ffxiv-login.square.localhost +127.0.0.1 patch-dl.ffxiv.localhost +``` + +On Windows this file is located under `C:\Windows\System32\Drivers\etc\hosts` and on Linux it's located under `/etc/hosts`. **If you plan on using Astra to connect to Kawari, this is not needed.** + ## Logging in Navigate to [http://ffxiv.localhost](http://ffxiv.localhost), and register for an account. In order to actually log in, navigate to the Setup page and follow the instructions there. If you get an error in your web browser, ensure you're connecting via **http://** and not **https://**.