Dear RT Gurus,
Our RT (3.8.2) on linux using virtual host on http
(http://rt.domainname.com) was
working fine. I moved RT over to httpS (https://rt.domainname.com) and got
the below message:
<<You’re almost there!
You haven’t yet configured your webserver to run RT. You appear to have
installed RT’s web interface correctly, but haven’t yet configured your web
server to “run” the RT server which powers the web interface. The next step
is to edit your webserver’s configuration file to instruct it to use RT’s
mod_perl, FastCGI or SpeedyCGI handler. If you need commercial support,
please contact us at sales@bestpractical.com. >>
Any clues? Am I missing anything in any configuration file? Below is my
ssl.conf configuration:
<VirtualHost *:443>
ServerName rt2.domainname.com
DocumentRoot /data/rt3/share/html
AddDefaultCharset UTF-8
PerlModule Apache::DBI
PerlRequire /data/rt3/bin/webmux.pl
<Location /NoAuth/images>
SetHandler default
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLRequireSSL
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/ssldir/server.crt
SSLCertificateKeyFile /etc/ssldir/server.key
Your probablems are not related to https, but enabling RT::Mason
handler for root directory. Read wiki for further understanding.On Mon, Aug 24, 2009 at 5:16 PM, testwreq wreqtestwreq@gmail.com wrote:
Dear RT Gurus,
Our RT (3.8.2) on linux using virtual host on http
(http://rt.domainname.com) was working fine. I moved RT over to httpS
(https://rt.domainname.com) and got the below message:
<<You’re almost there!
You haven’t yet configured your webserver to run RT. You appear to have
installed RT’s web interface correctly, but haven’t yet configured your web
server to “run” the RT server which powers the web interface. The next step
is to edit your webserver’s configuration file to instruct it to use RT’s
mod_perl, FastCGI or SpeedyCGI handler. If you need commercial support,
please contact us at sales@bestpractical.com. >>
Any clues? Am I missing anything in any configuration file? Below is my
ssl.conf configuration:
<VirtualHost *:443>
ServerName rt2.domainname.com
DocumentRoot /data/rt3/share/html
AddDefaultCharset UTF-8
PerlModule Apache::DBI
PerlRequire /data/rt3/bin/webmux.pl
<Location /NoAuth/images>
SetHandler default
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLRequireSSL
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/ssldir/server.crt
SSLCertificateKeyFile /etc/ssldir/server.key
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Best regards, Ruslan.
Dear RT Gurus,
Our RT (3.8.2) on linux using virtual host on http
(http://rt.domainname.com) was
working fine. I moved RT over to httpS (https://rt.domainname.com)
and got the below message:
<<You’re almost there!
You haven’t yet configured your webserver to run RT. You appear to
have installed RT’s web interface correctly, but haven’t yet
configured your web server to “run” the RT server which powers the
web interface. The next step is to edit your webserver’s
configuration file to instruct it to use RT’s mod_perl, FastCGI or
SpeedyCGI handler. If you need commercial support, please contact us
at sales@bestpractical.com. >>
Any clues? Am I missing anything in any configuration file? Below is
my ssl.conf configuration:
<VirtualHost *:443>
ServerName rt2.domainname.com
DocumentRoot /data/rt3/share/html
AddDefaultCharset UTF-8
PerlModule Apache::DBI
PerlRequire /data/rt3/bin/webmux.pl
<Location /NoAuth/images>
SetHandler default
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLRequireSSL
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite
ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/ssldir/server.crt
SSLCertificateKeyFile /etc/ssldir/server.key
Hey
Seems like u missing some stuff like:
SetHandler perl-script
PerlResponseHandler RT::Mason
Check out the Wiki Article on that:
http://wiki.bestpractical.com/view/ManualApacheConfig
Cheers
Tobias Lott
You are a true RT Guru and an apache genius.
Adding below in httpd.conf vhost section took care of the rewrite problem.
RewriteEngine ON
RewriteRule ^(.)$ https://rt.domainname.com/$1 [R=301,L]
If you can spare a min, can you please indicate what rule reads e.g the use
of ^. $1 etc?
http://rt.domainname.com redirect to https://rt.domainname.com// ; I think,
there is an extra slash after the domain name.On Mon, Aug 24, 2009 at 11:03 AM, Tobias lott tobias@lott.eu.org wrote:
On Mon, 24 Aug 2009 09:16:16 -0400 testwreq wreq testwreq@gmail.com wrote:
Dear RT Gurus,
Our RT (3.8.2) on linux using virtual host on http
(http://rt.domainname.com) was
working fine. I moved RT over to httpS (https://rt.domainname.com)
and got the below message:
<<You’re almost there!
You haven’t yet configured your webserver to run RT. You appear to
have installed RT’s web interface correctly, but haven’t yet
configured your web server to “run” the RT server which powers the
web interface. The next step is to edit your webserver’s
configuration file to instruct it to use RT’s mod_perl, FastCGI or
SpeedyCGI handler. If you need commercial support, please contact us
at sales@bestpractical.com. >>
Any clues? Am I missing anything in any configuration file? Below is
my ssl.conf configuration:
<VirtualHost *:443>
ServerName rt2.domainname.com
DocumentRoot /data/rt3/share/html
AddDefaultCharset UTF-8
PerlModule Apache::DBI
PerlRequire /data/rt3/bin/webmux.pl
<Location /NoAuth/images>
SetHandler default
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLRequireSSL
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite
ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/ssldir/server.crt
SSLCertificateKeyFile /etc/ssldir/server.key
Hey
Seems like u missing some stuff like:
SetHandler perl-script
PerlResponseHandler RT::Mason
Check out the Wiki Article on that:
ManualApacheConfig - Request Tracker Wiki
Cheers
–
Tobias Lott
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com