502 Bad Gateway: Difference between revisions
m Improve phrasing |
m Update that Tommy will also give 502 errors while doing hard restarts |
||
| Line 3: | Line 3: | ||
== Apache Restarts == | == Apache Restarts == | ||
Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Johnny|Johnny]] | Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting. | ||
The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after | The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server. | ||
To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents. | To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents. | ||
If you prefer not to have Apache restart, you can sign up for a [https://heliohost.org/vps/ VPS], where you can leave Apache or Nginx running for months without a restart. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront. | If you prefer not to have Apache restart, you can sign up for a [https://heliohost.org/vps/ VPS], where you can leave Apache or Nginx running for months without a restart. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront. | ||
Latest revision as of 05:23, 1 February 2025
502 Bad Gateway
Apache Restarts
Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the Tommy and Johnny servers, your site may display a 502 error to visitors. On the Morty server, a 504 error may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.
The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.
To check the status of our servers, please visit the visit the HelioHost Services Status Page. The status page provides a real-time overview of your server’s status and includes a history of past incidents.
If you prefer not to have Apache restart, you can sign up for a VPS, where you can leave Apache or Nginx running for months without a restart. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront.