Topics Map > Error Messages
Topics Map > Troubleshooting

WiscWeb - 502 Bad Gateway

This document will provide you with information on what the 502 bad gateway error looks like, what it means, and what you can do about it.

Example of Bad Gateway error


The 502 Bad Gateway error is shown when a Denial of Service (DoS) attack is suspected. Typically when a user sees this issue, it is because they have attempted to make too many updates on their site in rapid succession, thus flooding the WiscWeb service with so much traffic. This traffic is suspected to be malicious in nature, like a bot attack. The system will then block the requests, as a security measure.


This issue arises because the traffic is all associated with a single IP address. Therefore, changing your IP address can help resolve it. The easiest way to do so would be to disconnect and then reconnect to VPN.

These options can also help resolve the issue:

  1. If a single update is needed to be made, please wait at least 10 minutes before attempting to re-publish or save your changes. This should be long enough to allow things to normalize.

  2. If multiple updates are needed, please space them out by several seconds to avoid triggering this response.


  • Some users may find that opening multiple tabs or windows might expedite the process of updating several pages at once. However, this is one of the biggest culprits for triggering a 502 Bad Gateway error because it causes the number of requests to double, triple, etc., all at once. Therefore, this approach is not recommended.

Keywordsbad gateway, 502, updates, changes, save, publish, file, replace, denial of service, dos, outage   Doc ID105709
OwnerJenna K.GroupWiscWeb
Created2020-09-09 12:43 CSTUpdated2023-09-01 10:40 CST
SitesDoIT Help Desk, WiscWeb
Feedback  1   1