Any time! If you're in the San Francisco Bay Area at any point, I'd be happy to meet up for a beer :) I love meeting people who use Review Board.
Also, if you ever need even faster, more confidential support for urgent/emergency situations of any kind, we have some other support options you might want to look into. We try to provide good support here to everyone, but aren't always able to get to things on the list as fast as we can for those under support contracts. (Support e-mails from those under contracts notify our phones immediately and pester us with repeated phone calls, 24/7, until we address the e-mail, which is great if something bad happens at 3AM. Well, great for you, the customer. Less great for my sleep ;) If this sounds at all useful, we have some details on those options here: https://www.reviewboard.org/support/, and can tailor them further to meet any needs you have. Christian -- Christian Hammond President/CEO of Beanbag <https://www.beanbaginc.com/> Makers of Review Board <https://www.reviewboard.org/> On Fri, Jan 20, 2017 at 2:43 AM, Antonio Soldo <[email protected]> wrote: > Thank you very much. Setting environment variable in apache configuartion > and restarting it did not help, but your other suggestion did, so thumbs > up. > > Again, thank you very much for fast reply and great suggestions. > I owe you, at least, a beer :) > > On Friday, January 20, 2017 at 10:15:02 AM UTC+1, Christian Hammond wrote: >> >> Glad you found the cause, and that it wasn't anything concerning! Sounds >> like Slack owns that address, then. I tried resolving it before responding >> earlier, but couldn't figure out what it mapped to. >> >> We use Python's urllib2, which respects the http_proxy and https_proxy >> environment variables. You should be able to set these in Apache using: >> >> SetEnv http_proxy http://yourproxy/ >> SetEnv https_proxy https://yourproxy/ >> >> You'll then needed to restart Apache. >> >> If that fails for some reason, you can try setting the environment >> variables in $rbsitedir/htdocs/reviewboard.wsgi. >> >> Hope that helps! >> >> Christian >> >> -- >> Christian Hammond >> President/CEO of Beanbag <https://www.beanbaginc.com/> >> Makers of Review Board <https://www.reviewboard.org/> >> >> On Fri, Jan 20, 2017 at 12:15 AM, Antonio Soldo <[email protected]> >> wrote: >> >>> Thank You Christian for fast reply. >>> >>> We are not using gravatar images and I tried switching this option >>> on/off just in case, but it didn't work out. >>> Then I kept digging through every single option in admin dashboard and >>> found that one webhook for slack was activated. >>> I switched it off and boom, everything works smooth. Again, I am very >>> thankful for this effort and fast response as this actually made me think >>> and to look deeper and better. >>> >>> To completely answer to Your questions: >>> >>> *Q: You're seeing this server-side?*A: Yes, this is traffic on server >>> side. >>> >>> *Q:Is this only when posting a new change for review using command line >>> tools, or through the web UI?*A: Tried only through webUI, but I think >>> it would act same iff slack webhook is active. >>> >>> *Q: Do you see it when just browsing through the UI?*A: No, by browsing >>> through UI application works fine, its responsive and behaves as planned. >>> *Q:* >>> *Any chance you have a browser extension that might be accessing >>> something?*A: I performed same steps in Mozilla with some 3rd party >>> extensions and in Chrome with no extensions at all, and it behaved exactly >>> the same in both cases. >>> >>> *Q: Can you give me the exact command you ran?*A: On review request I >>> made some comment, and published it. After publishing it, it keeps the >>> 'Loading' banner active, and when trying to switch to any other screen, a >>> short popup is displayed with message 'HTTP 0 Error'. Application is again >>> in usable state, and everything works as expected until You try to publish >>> some change. >>> >>> >>> Apart from not using this webhook at all (it is a neat feature, but not >>> the reason to stop using ReviewBoard), is it possible to configure >>> ReviewBoard to channel every request through proxy server? >>> >>> Once again, thank You very much >>> >>> On Friday, January 20, 2017 at 5:04:44 AM UTC+1, Christian Hammond wrote: >>>> >>>> Hi Antonio, >>>> >>>> That's not one of our servers, from what I can tell, and there's >>>> nothing in our code referencing this at all. You're seeing this >>>> server-side? Is this only when posting a new change for review using >>>> command line tools, or through the web UI? Do you see it when just browsing >>>> through the UI? >>>> >>>> We do use https://secure.gravatar.com/, but I don't know whether this >>>> is served on CloudFront. >>>> >>>> If you're on the Admin UI page, we have a browser-side query to >>>> beanbaginc.com to check on the support level of the server. >>>> >>>> Any chance you have a browser extension that might be accessing >>>> something? >>>> >>>> Can you give me the exact command you ran? I'll see if it pops up on my >>>> end. >>>> >>>> Christian >>>> >>>> -- >>>> Christian Hammond >>>> President/CEO of Beanbag <https://www.beanbaginc.com/> >>>> Makers of Review Board <https://www.reviewboard.org/> >>>> >>>> On Thu, Jan 19, 2017 at 7:49 AM, Antonio Soldo <[email protected]> >>>> wrote: >>>> >>>>> I addition to my question, the reason I'm asking such thing is that we >>>>> have our instance of ReviewBoard (and any other tool hosted at us) behind >>>>> proxy, and all outgoing request must be channeled through this proxy. As >>>>> in >>>>> this case, proxy is bypassed (not consulted), and all outgoing public >>>>> network request are discarded. Because of this, application is slow (for >>>>> example, posting a comment in review takes up to 3 mins) and application >>>>> is >>>>> barely usable. >>>>> >>>>> As a continuation on first question, is there a possibility to run >>>>> reviewboard in such "eco-system" (where every public http request must go >>>>> through proxy)? >>>>> >>>>> What we tried is to set env variable http_proxy and https_proxy to >>>>> point at out proxy. Running command 'lynx gooogle.com' on CentOS that >>>>> backs ReviewBoard went through proxy and response was received. But >>>>> repeating comment publishing on review resulted in same manner as first >>>>> time, a direct request to cloudfront was made instead of going through >>>>> proxy. >>>>> >>>>> >>>>> >>>>> On Thursday, January 19, 2017 at 4:02:22 PM UTC+1, Antonio Soldo wrote: >>>>>> >>>>>> Hi all >>>>>> >>>>>> Is there a reason why is ReviewBoard trying to connect to the >>>>>> server-54-192-186-70.cdg51.r.cloudfront.net after every change that >>>>>> is published on review? >>>>>> I was monitoring my net traffic and noticed this connection and did >>>>>> not find anything specific why this server would be contacted. In my >>>>>> admin >>>>>> dashboard I defined that all files are hosted locally. >>>>>> Also, inspecting web server configuration did not give me any clue. >>>>>> I'm attaching captured traffic so everybody could see request made to >>>>>> above >>>>>> mentioned server. >>>>>> >>>>>> I'm hosting ReviewBoard locally, and currently running version 2.5.7 >>>>>> on CentOS 7.3.1611. ReviewBoard is run on Apache web server. >>>>>> >>>>>> Thank you in advance >>>>>> >>>>>> -- >>>>> Supercharge your Review Board with Power Pack: >>>>> https://www.reviewboard.org/powerpack/ >>>>> Want us to host Review Board for you? Check out RBCommons: >>>>> https://rbcommons.com/ >>>>> Happy user? Let us know! https://www.reviewboard.org/users/ >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "reviewboard" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> Supercharge your Review Board with Power Pack: >>> https://www.reviewboard.org/powerpack/ >>> Want us to host Review Board for you? Check out RBCommons: >>> https://rbcommons.com/ >>> Happy user? Let us know! https://www.reviewboard.org/users/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "reviewboard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "reviewboard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
