natebot13 / mongoose

Automatically exported from code.google.com/p/mongoose
MIT License
0 stars 0 forks source link

Mongoose Fails to start HTTPS under Windows #400

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download mongoose-3.8.exe to D:/mongoose
2. Start mongoose successfully for the first time.
3. Edit the setting by changing the listening port to 80,443s
4. Restart the mongoose and then mongoose fails to start.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
The Mongoose I am using is Mongoose 3.8, and the operating system is Windows XP 
and Windows 7.

Please provide any additional information below.
The message is "Fail to Start Mongoose"
If listen to port without 's', then the program works.
No application listening on port 443.

The following lines are in configuration file
listening_ports 80,443s
ssl_certificate D:\Mongoose\ssl_cert.pem

Original issue reported on code.google.com by tili...@gmail.com on 25 Jul 2013 at 3:03

GoogleCodeExporter commented 9 years ago
Just tried to reproduce it.

listening_ports 8080r,8443s
ssl_certificate c:\ssl_cert.pem

Connected to http://127.0.0.1:8080
Got redirected to SSL port. Works as expected.

Try to set error log file, and look at the errors you've got.

Original comment by valenok on 25 Jul 2013 at 5:48

GoogleCodeExporter commented 9 years ago
The error logs shows the following error message

[1374811358] [error] [client 0.0.0.0] mongoose.c:4767: cannot open 
D:\Mongoose\ssl_cert.pem:

I am trying to setup a server supporting both 80 and 443s.

Thanks.

Original comment by tili...@gmail.com on 26 Jul 2013 at 4:03

Attachments:

GoogleCodeExporter commented 9 years ago
Make sure ssl_cert.pem exists and is correct.
Use https://raw.github.com/valenok/mongoose/master/build/ssl_cert.pem and see 
if it works.

Original comment by valenok on 26 Jul 2013 at 4:37

GoogleCodeExporter commented 9 years ago
It works. 
Seems that something is wrong with the certification.
Thanks.

Original comment by tili...@gmail.com on 30 Jul 2013 at 7:37

GoogleCodeExporter commented 9 years ago
Your certificate file must have two things in it: a certificate and a private 
key.
Both in PEM format.

Original comment by valenok on 30 Jul 2013 at 8:10