Could not resolve io.fabric.tools:gradle:1.26.1.

[iamcootis]

I have the app working on my Windows 10 machine, but wanted to run both Android and IOS at the same time, so I got a Mac and began porting over the app. tns doctor is returning that everything is OK, but I keep getting this error when trying to run android:

 Could not resolve all artifacts for configuration ':classpath'.
   > Could not resolve io.fabric.tools:gradle:1.26.1.
     Required by:
         project :
      > Could not resolve io.fabric.tools:gradle:1.26.1.
         > Could not get resource 'https://maven.fabric.io/public/io/fabric/tools/gradle/1.26.1/gradle-1.26.1.pom'.
            > Could not GET 'https://maven.fabric.io/public/io/fabric/tools/gradle/1.26.1/gradle-1.26.1.pom'.
               > Connect to maven.fabric.io:443 [maven.fabric.io/0.0.0.0, maven.fabric.io/0:0:0:0:0:0:0:0] failed: Connection refused (Connection refused)

"dependencies": {
    "@angular/animations": "~8.2.0",
    "@angular/common": "~8.2.0",
    "@angular/compiler": "~8.2.0",
    "@angular/core": "~8.2.0",
    "@angular/forms": "~8.2.0",
    "@angular/platform-browser": "~8.2.0",
    "@angular/platform-browser-dynamic": "~8.2.0",
    "@angular/router": "~8.2.0",
    "nativescript-angular": "~8.2.0",
    "nativescript-imagepicker": "^7.1.0",
    "nativescript-plugin-firebase": "^10.3.3",
    "nativescript-theme-core": "~1.0.6",
    "nativescript-ui-autocomplete": "^6.0.0",
    "nativescript-ui-sidedrawer": "^8.0.0",
    "reflect-metadata": "~0.1.12",
    "rxjs": "^6.4.0",
    "tns-core-modules": "^6.4.0",
    "zone.js": "~0.9.1"
  },
  "devDependencies": {
    "@angular/compiler-cli": "~8.2.0",
    "@ngtools/webpack": "8.2.0",
    "codelyzer": "~4.5.0",
    "nativescript-dev-webpack": "^1.5.0",
    "node-sass": "^4.7.1",
    "tslint": "~5.19.0",
    "typescript": "~3.5.3"
  }

[EddyVerbruggen]

Hi, did you try opening https://maven.fabric.io/public/io/fabric/tools/gradle/1.26.1/gradle-1.26.1.pom in a browser or on a different machine? Your device logs it can't access the URL, but it seems to be available just fine.

[iamcootis]

Thanks, this led me down the right track. I was running a pihole that was preventing this from being reached. Somehow it worked from my Windows machine, but not my Mac. I disabled, the pihole and it worked.