[rt-users] rt-mailgate https - problem
Hello, I have following problem: root@rt:~# rt-mailgate --debug --action correspond --url= https://localhost/rt --queue General /root/test.msg /usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW' /usr/bin/rt-mailgate: connecting to https://localhost/rt/REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Can't connect to localhost:443 /usr/bin/rt-mailgate: undefined server error root@rt:~# On my RT-server I can't checkin the tickets via https (https website via browser works fine - certificte is ok) - via http it works fine! The Apache errorlog is empty. what does this error mean? Best Regards -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] rt-mailgate https - problem
Hello, I have following problem: root@rt:~# rt-mailgate --debug --action correspond --url= https://localhost/rt --queue General /root/test.msg /usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW' /usr/bin/rt-mailgate: connecting to https://localhost/rt/REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Can't connect to localhost:443 /usr/bin/rt-mailgate: undefined server error root@rt:~# On my RT-server I can't checkin the tickets via https (https website via browser works fine - certificte is ok) - via http it works fine! The Apache errorlog is empty. what does this error mean? Best Regards -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate https - problem
Replace in the URL parameter to rt-mailgate localhost with the FQDN. Chris Am 30.06.2014 11:17, schrieb DD DD: Hello, I have following problem: root@rt:~# rt-mailgate --debug --action correspond --url=https://localhost/rt --queue General /root/test.msg /usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW' /usr/bin/rt-mailgate: connecting to https://localhost/rt/REST/1.0/NoAuth/mail-gateway An Error Occurred = 500 Can't connect to localhost:443 /usr/bin/rt-mailgate: undefined server error root@rt:~# On my RT-server I can't checkin the tickets via https (https website via browser works fine - certificte is ok) - via http it works fine! The Apache errorlog is empty. what does this error mean? Best Regards -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate https - problem
Please keep replies to the list. Which RT version are you using? Because your apache making a redirect and rt-mailgate following redirects only in RT 4.2.4 and newer. Chris Am 30.06.2014 12:09, schrieb DD DD: root@rt:~# wget https://HIDDEN/rt --2014-06-30 12:04:42-- https://HIDDEN/rt Resolving HIDDEN (HIDDEN)... HIDDEN Connecting to HIDDEN (HIDDEN)|HIDDEN|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://HIDDEN/rt/ [following] --2014-06-30 12:04:42-- https://HIDDEN/rt/ Reusing existing connection to HIDDEN:443. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: `rt' [ = ] 4,064 --.-K/s in 0.01 2014-06-30 12:04:43 (324 KB/s) - `rt' saved [4064] root@rt:~# It seems that Apache doesn't listen correct, but the hosts entry is correct. -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate https - problem
on old and new server there runs 4.0.7 new machine: root@rt:~# wget https://127.0.0.1/rt --2014-06-30 12:24:15-- https://127.0.0.1/rt Connecting to 127.0.0.1:443... connected. The certificate's owner does not match hostname `127.0.0.1' root@rt:~# wget https://localhost/rt --2014-06-30 12:28:22-- https://localhost/rt Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:443... connected. GnuTLS: A TLS warning alert has been received. Unable to establish SSL connection. root@rt:~# Why occurs a TLS warning? This comes not from the certificate (I also tried it with --no-check-certificate) 2014-06-30 12:21 GMT+02:00 Christian Loos cl...@netcologne.de: Please keep replies to the list. Which RT version are you using? Because your apache making a redirect and rt-mailgate following redirects only in RT 4.2.4 and newer. Chris Am 30.06.2014 12:09, schrieb DD DD: root@rt:~# wget https://HIDDEN/rt --2014-06-30 12:04:42-- https://HIDDEN/rt Resolving HIDDEN (HIDDEN)... HIDDEN Connecting to HIDDEN (HIDDEN)|HIDDEN|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://HIDDEN/rt/ [following] --2014-06-30 12:04:42-- https://HIDDEN/rt/ Reusing existing connection to HIDDEN:443. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: `rt' [ = ] 4,064 --.-K/s in 0.01 2014-06-30 12:04:43 (324 KB/s) - `rt' saved [4064] root@rt:~# It seems that Apache doesn't listen correct, but the hosts entry is correct. -- RT Training - Boston, September 9-10 http://bestpractical.com/training
