Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal error: connect ETIMEDOUT #36

Open
emkayy opened this issue Feb 15, 2017 · 4 comments
Open

Fatal error: connect ETIMEDOUT #36

emkayy opened this issue Feb 15, 2017 · 4 comments

Comments

@emkayy
Copy link

emkayy commented Feb 15, 2017

Hi there,

when I try to run the realFavicon grunt task, I'm getting the following error

Running "realFavicon:favicons" (realFavicon) task
Generating "src/favicon/logo.png" favicon...Fatal error: connect ETIMEDOUT 5.196.181.96:80

Why does it have to connect to any server? What server is it?
I'm behind a corporate firewall, maybe that's the problem?

Any suggestions how I can fix this?

@phbernard
Copy link
Contributor

Hi,

The service is RealFaviconGenertor's. The icons are generated through an API.

There was no issue recently, so I don't see why the service would have failed that way.

Because this is the very same site you visited in the first place (https://realfavicongenerator.net/) with your browser, your firewall shouldn't block it. However, if it is tricky enough, it might block is. For example, the API client doesn't use a regular user agent string (ie. its neither Chrome, nor Firefox, etc.). If you have a good support team, I suggest you to ask them.

Does this help?

@Huntedpix
Copy link

Hi,

I've the same issue here.

Running "realFavicon:favicons" (realFavicon) task
Generating "src/img/favicons/master.png" favicon...Fatal error: connect ETIMEDOUT 5.196.181.96:443

Unfortunately, the Firewall team in my company will not allow it.

Is there a way to set a proxy settings via the options ?

@phbernard
Copy link
Contributor

There is no such option in the plugin, sorry.

Is there a global proxy setting for Node or Grunt? After all, this is a common case and you want your whole environment to use the same proxy.

@Huntedpix
Copy link

Hi !

There is a global proxy setting for NPM, but I haven't found any for Node or Grunt.

But your comment give me some new idea and I've found a solution to make your plugin work ! :)

I install this node module (not global install): https://github.com/np-maintain/global-tunnel

Then I set at the beginning of my Gruntfile.js the module.

var globalTunnel = require('global-tunnel-ng')
globalTunnel.initialize({
  host: 'proxy',
  port: 8080
})

So every outside call from Node is using my corporate proxy and your plugin work.

Thanks for the idea !

@emkayy I hope this will help you too ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants