Good Afternoon Guys -
I've used Serv-U at the company I work for for a while now - but only as a plain-jane FTP server. Only after stumbling across some settings in the console did I find out the potential which wasn't being used. Since then, I've set up the web console and am excited about it's features. One thing that's manditory is enabling SSL for the web traffic, though. I can't get it to work correctly, though.
The Issue
When I try to go to "https://servuserver" or https://servuserver:443", it times out. However, I can successfully navigate to http://servuserver:443 which is strange. I get the same results when using the IP instead of hostname. I am attempting the connection from a system on the LAN. I've tried many things, but can't get it to work over HTTPS.
Serv-U's Current Setup
Below are the current settings I have established which pertain to HTTPS / Port 443:
- Couldn't find Serv-U version, but was installed within past 6 months
- Currently run on Windows 7 x64 "server" which hosts 4-5 additional web services (all on different ports which do not conflict)
- Domain Details / Listeners: Listener for port 443 set to default of HTTPS (SSL encrypted HTTP)
- Limits & Settings / SSL Certificate: Created SSL Certificate via wizard in Serv-U and saved to new folder in Rhinosoft folder. When done, chose to have it apply the newly created cert. Both paths and password are filled out as you can see below (made SSH one, too)
HTTP Info
I don't know if it makes a difference, but on the server Serv-U is installed on, port 80 was already being used therefore I reassigned HTTP to port 81 via the listener. When browsing to 81 (http://servuserver:81), everything seemingly works as it is supposed to including the Java Voyager client.
What I've Tried to Fix
- Changed the HTTPS listener from 443 to 444 - I thought perhaps if 80 already had a conflict, perhaps 443 did too. After changing, browsing to https://servuserver:444 timed out as well
- Tried adding a new listener set up as HTTPS but set to a random port of 777. Same results as it timed out, too
- Created a new certificate via wizard as
- Created a certificate via 3rd party site which can be converted if needed at this site
Nothing worked. I know I could purchase one, but for now this service would only be used by a couple of people for proof of concept. More than likely it's something simple I'm missing.
Any ideas? Thanks!