Skip to content

connect ETIMEDOUT 172.217.13.234:443 - Even after analytics are off #19259

Closed

Description

@vjangari

🐞 Bug report

Command (mark with an x)

  • new
  • [X ] build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

Description

A clear and concise description of the problem...

ng build --prod -> build trying to connect google server despite of switch off analytics
ng analytics off
also we tried angular.json file

connect ETIMEDOUT 172.217.13.234:443

Activity

  1. alan-agius4 commented on Oct 29, 2020

    @alan-agius4
    Collaborator

    @vjangari,

    Can you please provide the output of ng version?

  2. vjangari commented on Oct 29, 2020

    @vjangari
    Author

    image

  3. vjangari commented on Oct 29, 2020

    @vjangari
    Author

    ng build is working fine. However ng build --prod is failing on CI server with error connect ETIMEDOUT 172.217.13.234:443 after creating build artifacts

  4. modified the milestone: needsTriage on Oct 29, 2020
  5. self-assigned this
    on Oct 29, 2020
  6. alan-agius4 commented on Oct 29, 2020

    @alan-agius4
    Collaborator

    Likely this is related to the new fonts optimizations which requires internet access during the build. Can you confirm that you are referencing Google fonts and/or icons in your html file?

    We should be showing a more actionable error in this case.

  7. added
    freq1: lowOnly reported by a handful of users who observe it rarely
    on Oct 29, 2020
  8. modified the milestones: needsTriage, Backlog on Oct 29, 2020
  9. vjangari commented on Oct 29, 2020

    @vjangari
    Author

    Yes I am using below link
    `
    link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500&display=swap" rel="stylesheet"
    link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet"

    `
    Same build is working fine with below dev dependencies. But not with rc1 versions

    "@angular-devkit/build-angular": "0.1100.0-next.5",
    "@angular/cli": "11.0.0-next.5",
    "@angular/compiler-cli": "11.0.0-next.5",

  10. alan-agius4 commented on Oct 30, 2020

    @alan-agius4
    Collaborator

    In case your build server don't have access to internet, you'd want to disable the inline fonts optimization.

    This can be done by via the optimization option in your browser builder configuration.

    - "optimization": true,
    + "optimization": {
    +   "styles": true,
    +   "scripts": true,
    +   "fonts": {
    +     "initial": false
    +   }
    + },
  11. vjangari commented on Oct 30, 2020

    @vjangari
    Author

    Getting below error
    Schema validation failed with the following errors:
    Data path ".optimization" should be boolean.

  12. alan-agius4 commented on Oct 30, 2020

    @alan-agius4
    Collaborator

    Can you share the build section of your angular.json?

  13. vjangari commented on Oct 30, 2020

    @vjangari
    Author

    "production": { "fileReplacements": [ { "replace": "src/environments/environment.ts", "with": "src/environments/environment.prod.ts" } ], "optimization": true, "outputHashing": "all", "sourceMap": false, "namedChunks": false, "extractLicenses": true, "vendorChunk": false, "buildOptimizer": true "extraWebpackConfig": "webpack.prod.config.js" },

  14. alan-agius4 commented on Oct 30, 2020

    @alan-agius4
    Collaborator

    Looks like you are not using an official Angular CLI builder.

    Kindly open an issue in the issue tracker of 3rd party builder.

  15. vjangari commented on Oct 30, 2020

    @vjangari
    Author

    ok. Sure. I am trying Module Federation with webpack 5 support. I will open ticket in corresponding repo. When can we expect official support for webpack 5 in angular cli?

  16. alan-agius4 commented on Oct 30, 2020

    @alan-agius4
    Collaborator

    Experimental opt-in support for Webpack version 5 have been added since v11.0.0-next.3.

    See #18820 for more information.

    For module federation support kindly subscribe to #17556

  17. added 2 commits that reference this issue on Nov 2, 2020
    6cd97b3
    d10cf91
  18. angular-automatic-lock-bot commented on Dec 3, 2020

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  19. locked and limited conversation to collaborators on Dec 3, 2020
  20. added a commit that references this issue on May 29, 2026
    b5e06c4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions