I was able to finally get trac to work, I had to use port 80 instead for
stunnel, not sure why. Also, since I'm using SUSE 11.1 that has python 2.6
and SUSE does not yet have a 11.3 rpm I installed the svn version of trac
and almost everything seems to work fine. The only problem that I'm having
now is, for example, when I edit a milestone and then submit the changes,
the progress bar just gets stuck at about half way when loading (it will
eventually time out with problem loading the page), but if I click on the
roadmap button (before it times out) it reloads the page with my changes
just fine. It seems to get stuck refreshing the page. Similar thing happens
when I log in, it just hangs on the current page, but if I click on any of
the buttons it shows me logged in. So information gets sent but not received
back automatically.

On Mon, Feb 9, 2009 at 8:13 AM, Flatfender <[email protected]> wrote:

>
> This sounds like a internal/external DNS issue
>
> On Fri, Feb 6, 2009 at 12:30 PM,  <[email protected]> wrote:
> >
> > Hi,
> >
> > I followed the directions outlined in
> >
> > http://trac.edgewall.org/wiki/STunnelTracd
> >
> > for setting up tracd + stunnel. Everything works perfectly if I
> > connect from different machines with the same last 2 suffixes in the
> > domain name (ex. .usc.edu) as the server, but when I try to connect
> > from a machine with a completely different domain name it never loads
> > the page. I tried it by disabling the firewall and removing
> > everything  in hosts.deny so that anything can connect but still the
> > same problem. Can someone suggest how I can track down where the
> > problem is when trying to connect from a different domain. Firefox
> > does not give any information that is useful.
> >
> > For SUSE 11.1:
> > I'm using: stunnel 4.25 on i686-suse-linux-gnu with OpenSSL 0.9.8h 28
> > May 2008
> > tracd 0.11.2
> >
> > when I do netstat I see the ports are available:
> >
> > tcp        0      0 127.0.0.1:8992          0.0.0.0:*
> > LISTEN      3788/python
> > tcp        0      0 0.0.0.0:8993            0.0.0.0:*
> > LISTEN      3608/stunnel
> >
> > >
> >
>
> This sounds like a internal/external DNS issue.  As in the two servers
> that are in your domain point to a internal DNS server which resolves
> things fine, and the external domain box sees external DNS and times
> out.  Does the external domain name box resolve things ok?  Do things
> work via IP?   What do the routes on each box look like.   Oh, and i
> didn't read the link above, I'm just guessing on possible networking
> causes. :)
>
> Matt P.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to