Tools

Getting an error "400 Bad Request" when accessing the Serv-U Web client

This article describes how to resolve error 400 Bad Request.

First published date

7/29/2021 12:04 AM

Last published date

10/14/2025 1:08 PM

Overview

Some users may encounter the error "400 Bad Request" when accessing the Serv-U Web client. 

The issue will typically occur in Serv-U instances where  multiple domains have been configured, with/without a Virtual Host.

image.png

or 

HTTP ERROR 400

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

In Serv-U, Virtual Host has a new option named "Require the HOST Header of HTTP requests to match the virtual hostname."
If this is active, Serv-U will only be accessible using the Virtual Hostname, ergo connections via IP or hostname of the Serv-U server would result in error 400 Bad Request. 

Resolution

  1. Log in to the Serv-U Management console
  2. Navigate to the Domain Details menu.
  3. Select Virtual Hosts.
  4. Deselect/Uncheck Require the HOST Header of HTTP requests to match the virtual hostname.

 image.png