That's a little bit different flavor than I'm having. I was seeing tickets in the user app. I was already logged in to the admin app.
If I clicked on the link to open the ticket in the user app, I would get the forbidden page. From there if I changed the protocol to https I could see the ticket. Maybe the same trick will work for you. Of course it's not really a fix anyway, just a work-around I discovered. On Sep 30, 9:10 am, Johann Spies <johann.sp...@gmail.com> wrote: > On 29 September 2011 15:57, Cliff <cjk...@gmail.com> wrote: > > > set up shows this error: > > > cjk@littlecliffsite:~$ channel 3: open failed: connect failed: > > Connection refused > > channel 3: open failed: connect failed: Connection refused > > > Any suggestions? > > I am having the same problem to a webfaction server. Don't know about their > ssh-forwarding setup on the other side. > > I need to find out the particulars about an 'Internal Error' and my admin > app gives me constant tickets whenever I want to access the tickets. > > Regards > Johann > > -- > May grace and peace be yours in abundance through the full knowledge of God > and of Jesus our Lord! His divine power has given us everything we need for > life and godliness through the full knowledge of the one who called us by > his own glory and excellence. > 2 Pet. 1:2b,3a
