Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

241
Views
How to discard browser messages for fetch calls failing at DNS/TCP level (not server error code)?

I wanted to have in the console custom messages for fetch issues and thought that catching them would be enough:

fetch("https://thissitedoesnotexist.wazaa")
  .then((response) => {
    if (!response.ok) {
      throw Error(response.status);
    }
    console.log("Result: ", response);
  })
  .catch((error) => {
    console.log("Something went wrong: ", error.message)
  });

What I get, however, are two console messages: one from the browser itself telling that the name is not resolved, and then my custom message:

Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Something went wrong:  Failed to fetch

Is there a way to discard the browser message?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!