Bug #2601
closedthen website reload automaticaly when i start wthttpd on 80 and 443 port
0%
Description
then website reload automaticaly when i start wthttpd on 80 and 443 port
Files
Updated by Koen Deforche over 10 years ago
Hey,
Can you be more specificaties on what you are exactly doping and seeing?
Regards,
Koen
Updated by Marcio Sales over 10 years ago
when i run wt app individually on port 80 and another instance on 443 no problema
but when a run on the same wt app browser reaload always
I think if u run any application with ssl wt and also enabled the port 80 problem will happen
sudo ./portal.wt ---docroot . ---http-address 0.0.0.0 ---http-port 80 ---https-address 0.0.0.0 ---https-port 443 ---ssl-certificate "/opt/keystore/server.crt" ---ssl-private-key "/opt/keystore/server.pem" ---ssl-tmp-dh "/opt/keystore/serverdh.pem"
BR
Márcio
Updated by Koen Deforche about 10 years ago
- Status changed from New to Feedback
Hey,
I just confirmed that this does work correctly for me. Some more information will be needed to understand what's wrong on your side?
Regards,
koen
Updated by Marcio Sales about 10 years ago
Hey
if i run wt app with this command line: ./portal.wt ---docroot . ---http-address 0.0.0.0 ---http-port 80
no problem.
if i run wt app with this command line: ./portal.wt ---docroot . ---https-address 0.0.0.0 ---https-port 443 ---ssl-certificate "/opt/keystore/server.crt" ---ssl-private-key "/opt/keystore/server.pem" ---ssl-tmp-dh "/opt/keystore/serverdh.pem"
no problem.
if i run wt app with this command line: ./portal.wt ---docroot . ---http-address 0.0.0.0 ---http-port 80 ---https-address 0.0.0.0 ---https-port 443 ---ssl-certificate "/opt/keystore/server.crt" ---ssl-private-key "/opt/keystore/server.pem" ---ssl-tmp-dh "/opt/keystore/serverdh.pem"
the problem occurs.
BR
Márcio
Updated by Koen Deforche about 10 years ago
Hey,
We'll need more information: log files (err log and access log), etc...
Regards,
koen
Updated by Marcio Sales about 10 years ago
- File wt_app.log wt_app.log added
Hey,
i execute on separate server and no problem.
i execute on production server and then problem occurs
see the log,
i examined the log and i think that the error is the same of this: [[[http://redmine.emweb.be/issues/2090]]]
BR
Márcio
Updated by Koen Deforche about 10 years ago
- Status changed from Feedback to Resolved
- Assignee set to Koen Deforche
- Target version changed from 3.3.1 to 3.3.2
Updated by Marcio Sales about 10 years ago
Hey
Very thanks, I think to be perfect for me, need to solved this issue:
http://redmine.emweb.be/issues/2582
BR
Márcio
Updated by Koen Deforche about 10 years ago
- Status changed from Resolved to Closed