#2009: Catwalk connection polling
----------------------------
+-----------------------------------------------
 Reporter:  paigeadele      |        Owner:  anonymous
     Type:  defect          |       Status:  new
 Priority:  normal          |    Milestone:  1.1
Component:  Toolbox         |      Version:  1.0.7
 Severity:  normal          |   Resolution:
 Keywords:  needs feedback  |
----------------------------
+-----------------------------------------------
Comment (by paigeadele):

 OK, so this is what you do:

 setup a vhost in apache that uses mod proxy on a server different
from the
 box you're going to be working from like this:

 <VirtualHost *:80>
        #DocumentRoot /home/erratic/public_html/
        #<Directory "/home/erratic/public_html/">
        #       Options Indexes FollowSymLinks
        #       AllowOverride All
        #       Order allow,deny
        #       Allow from all
        #</Directory>
        #ErrorLog logs/evilx.devel.ws.error.log
        #CustomLog logs/evilx.devel.ws.custom.log combined
        ServerName catwalk.devel.ws
        UseCanonicalName Off
        ServerSignature Off
        ProxyPass / http://127.0.0.1:7654/
        ProxyPassReverse / http://127.0.0.1:7654/
        ProxyPreserveHost On
        ProxyRequests Off
        ProxyPass /error/ !
        ProxyPass /icons/ !
        ProxyPass /favicon.ico !
        #ProxyPass /static/ !
        AddDefaultCharset utf-8

 </VirtualHost>

 Now, start the catwalk server and make sure it runs on port 7654 (The
 default for the installation I had) Now open up your web browser and
point
 it to your equivalent of "catwalk.devel.ws" which keep in mind you're
not
 running the web browser on the same machine as the server thats
running
 catwalk and mod_proxy. It will give you this message:


      No access for ::ffff:127.0.0.1

 By default only localhost (127.0.0.1) has access to the Toolbox

 You can provide access to your client by passing your host address to
 Toolbox as a parameter. Ex:

                tg-admin toolbox -c ::ffff:127.0.0.1


 However when you do this it still gives you the same message: unless
you
 specify for example in my case -c 75.165.82.108
 Which is what it should suggest, but doesn't because it's polling
 connections in a different way than it's evaluating them or else
 specifying -c 75.165.82.108 wouldn't work--which it does. Please get
back
 to me if this doesn't explain it, though I can't really think of a
better
 way to explain it...

-- Ticket URL: <http://trac.turbogears.org/ticket/2009#comment:2>
TurboGears <http://www.turbogears.org/> TurboGears front-to-back web
development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to