Hey Denard
  I made a mistake in my text. Actually I am behind corporate proxy ...i 
wrongly wrote corporate firewall! Apologoies.
   Does your reply still hold true for Corporate proxy also OR there is a 
way i can make it work if my request is originating from behind a corporate 
proxy ?


On Friday, June 24, 2016 at 5:38:43 AM UTC+5:30, Denard Springle wrote:
>
> Hey Dinesh,
>
>    If you're behind a corporate firewall then proxy will not help you as 
> you will still be unable to establish an http connection with the proxy 
> from behind the firewall (which is blocking your outside access). Also, 
> since you're trying to connect to a database, a proxy will not help you 
> because it's an http proxy, not a tcp proxy and (most) database connections 
> don't (typically) use http. 
>
>    The solution is to adjust the corporate firewall to allow your server 
> access to the internet, in general, or at least to the cloud based database 
> port, if nothing else.
>
>    In short, this is a dev ops or IT issue and needs to be resolved by 
> whomever handles managing the firewall for your corporation.
>
> HTH!
>
> -- Denny
>
> On Wednesday, June 22, 2016 at 8:50:40 AM UTC-4, Dinesh Rampal wrote:
>>
>> Hi
>>
>> I have a application which works fine, but when i try to make it work in 
>> office behind a corporate firewall, it fails to make a call to a internet 
>> cloud based database. Querying in Google, i found that i need to set up 
>> config parameters - *proxy and https-proxy*.
>>
>> npm config set proxy http://proxy.company.com:8080
>> npm config set https-proxy http://proxy.company.com:8080
>>
>>
>> I have done the above commands in all possible combinations, but it 
>> doesn't work.
>>
>> Can somebody tell me how can i come around this problem ? Is this the 
>> only way to solve this OR there are solutions to my issue.
>>
>> The exception which i get is -  
>>             event.js : 85
>>             
>>             throw er; // Unhandled 'er' event.
>>
>>             Error : connect ETIMEDOUT
>>
>>                          at exports._ErrnoExcpetion <util.js:746:11>
>>                           at TCPConnectWrap.afterConnect [as Oncomplete] 
>> <net.js:1010:19>
>>
>> My project is at stake.
>>
>> Will appreciate all help.
>>
>> thanks a lot
>>
>> regards
>> dinesh
>>
>>
>>
>>
>>
>>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/723718ff-00c8-43cc-af8a-8783516f9025%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to