Looks like I spoke to soon about my IPN solution, for some bizarre reason, it stops working as soon as take the server out of development mode. I think this must have something to do with deployment setups that is over my head, so any clues appreciated.
I am deployed using mod_proxy and mod_rewrite. The site has been working fine this way for months. The ipn method is at: http://www.staging.sitename.org/payment/ipn hitting this manually works, no matter how I start the server. I get a record in my ipn log table that I am making, of course it doesn't verify but I can see that the method got hit. When I start the server in dev mode through a terminal, paypal hits it fine and everything goes according to plan. But when I switch to production, it seems that paypal never hits the method. No ipn record. My apache access logs still show this: 66.211.170.66 - - [23/Apr/2008:14:36:39 -0700] "POST /payment/ipn HTTP/1.0" 500 35 "-" "-" 66.211.170.66 - - [23/Apr/2008:14:37:01 -0700] "POST /payment/ipn HTTP/1.0" 500 35 "-" "-" Does anyone know what might be different between dev mode and production started backgrounded? I'm starting them with the same user, and in each case the site is being accessed through a proxied domain name, not with the port number. ( ie ./start-site.py site-prod.cfg & ) I'm stumped! Thanks Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
