Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Configure Serv-U for access from a web browser

Configure Serv-U for access from a web browser

Updated March 30, 2017

Overview

This article provides information and steps to configure HTTP/S listener and log on via FTP interface browser.

 

Environment

Serv-U 14.0 and later

Steps

Configure the HTTP/HTTPS Listener

  1. Go to Domain Details > Listeners.
  2. Click Add.
  3. Select HTTP or HTTPS for secured HTTP in the Type drop-down menu. Insert image after last step. 
  4. Select the IP for your listener, and then click Save. 

Once users log on to the HTTP listener by browsing to your domain name or IP address, they will be able to log on using the Serv-U interface (demo available online at the Serv-U Demo Server). If their Default Web Client has not already been specified and the FTP Voyager JV has been purchased, they will be prompted to select whether they wish to use the Web Client or FTP Voyager JV. 

Notes:

  • The Serv-U HTTP and HTTPS Listeners are responsible for providing clients with access to the Web Client and FTP Voyager JV (if installed). These two listeners are configured the same as any of the other listeners in Serv-U.
  • If the server that Serv-U is installed on is also running a web server on port 80 (which is the web server default), Serv-U's HTTP Listener and the web server may interfere with each other. This can be resolved by configuring the HTTP listener to use a different port (such as 8080, requiring users to connect to your Serv-U server at http://www.yourdomain.com:8080), or assigning multiple IP addresses to your server and specifying one IP address for Serv-U to use and a different IP address for the web server to use. 
  • If Serv-U is installed on a network which uses NAT and that same network is also running a web server, the network's router is likely already forwarding port 80 to the web server and will not be able to specifically send Serv-U requests to Serv-U. In this case, Serv-U MUST run on a different port number such as 8080 and the router must forward port 8080 to Serv-U. 
  • In order for the HTTPS listener to operate, an SSL certificate must be configured in Domain Limits & Settings | Encryption.

Adding an HTTP listener

Log on using a browser FTP interface

This format allows browsers to connect to the Serv-U FTP listener:

ftp://userid:password@site:port

  • userid - the user id to be used for the connection
  • password - the password used in conjunction with the userid
  • site - the FTP server name or IP address
  • port - if the port number is not 21, specify the port number here

 

 

Last modified
21:11, 16 Apr 2017

Tags

Classifications

Public