fix: healthcheck hostname (#616)

* fix: healthcheck hostname * Update healthchecks-and-restarts.md --------- Co-authored-by: Brody Over <[email protected]>
railwayapp · Nov 24, 2024 · 6399260 · 6399260
1 parent 19744f5
commit 6399260
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/src/docs/guides/healthchecks-and-restarts.md b/src/docs/guides/healthchecks-and-restarts.md
@@ -48,9 +48,9 @@ To prevent data corruption, we prevent multiple deployments from being active an
 
 ### Healthcheck Hostname
 
-Railway uses the hostname `healthcheck.railway.com` when performing healthchecks on your service. This is the domain from which the healthcheck requests will originate.
+Railway uses the hostname `healthcheck.railway.app` when performing healthchecks on your service. This is the domain from which the healthcheck requests will originate.
 
-For applications that restrict incoming traffic based on the hostname, you'll need to add `healthcheck.railway.com` to your list of allowed hosts. This ensures that your application will accept healthcheck requests from Railway.
+For applications that restrict incoming traffic based on the hostname, you'll need to add `healthcheck.railway.app` to your list of allowed hosts. This ensures that your application will accept healthcheck requests from Railway.
 
 If your application does not permit requests from that hostname, you may encounter errors during the healthcheck process, such as "failed with service unavailable" or "failed with status 400".
 
@@ -72,4 +72,4 @@ To configure a restart policy, go to the Service settings, set a restart policy
 
 - `On-Failure`: Railway will only restart your service if it stops due to an error (e.g., crashes, exits with a non-zero code). This is a good option if you want to avoid unnecessary restarts when the service stops intentionally.
 
-- `Never`: Railway will never automatically restart your service, even if it crashes. This is typically used for one-off tasks or scheduled jobs where you don't want the service to keep running after it completes.
+- `Never`: Railway will never automatically restart your service, even if it crashes. This is typically used for one-off tasks or scheduled jobs where you don't want the service to keep running after it completes.