Tools

Unable to access Serv-U using HTTP and HTTPS

This article shows how to troubleshoot a problem where Serv-U HTTP and HTTPS is not accessible

First published date

9/27/2019 3:25 PM

Last published date

9/27/2019 4:05 PM

Overview


Serv-U HTTP and HTTPS pages does not load internally or externally. 
A number of error might show but the most common one is: This site can’t be reached

Product section

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

Cause

Resolution






  • To isolate an SSL issue, set the certificate, private key and password fields to blank and SAVE. Now Serv-U will be forced to use it's default self-signed certificate. Try to load the HTTP or HTTPS site. 
  • The Serv-U domain logs will also show an entry where it cannot see the certificate or private key files when an HTTPS connection attempt is made.



  • When the 'Require secure connection before login' option is enabled, all HTTP connections will be redirected to HTTPS
  • If there is no HTTPS listener configured, then the HTTP connection attempt will fail
  • Go to Global > Domains > Limits & Settings > Limits tab
  • Under the 'Connection' Limit Type, disable 'Require secure connection before login'
  • OR
  • Configure an HTTPS listener in Domains > Domain Details > Listener tab > ADD > HTTPS port 443

  • Disable IIS from the server. Serv-U does not need IIS to run.
  • Go to the Windows Services Console (services.msc) and look for the World Wide Web service. Stop this service and set the start up type to Disabled.