Railway•2y ago

AxiosError: connect ECONNREFUSED 127.0.0.1:80

I have a nodejs application and I have a axios inside it, because I need to call a api to populate the response of my api, but when I deployed my application, I'm getting this error from axios, someone know what is it?

49 Replies

Percy•2y ago

Project ID: N/A

Percy•2y ago

You might find these helpful: - Code Runs on Localhost but Uncaught Syntax Error After Deployment - 404 Error

⚠️ experimental feature

Brody•2y ago

This could be a lot of things, could I see a repo please?

lucaszdevmmyers616OP•2y ago

N/A It's private, but I can send the Axios call: const request = axios.create({ baseURL, timeout: 10000, // 10s timeout headers: { Accept: "application/json", "Content-Type": "application/json" }, }); I'm only getting request and using axios normally

Brody•2y ago

What's the baseURL set to

lucaszdevmmyers616OP•2y ago

the url of the api I want to call

Brody•2y ago

and that is?

lucaszdevmmyers616OP•2y ago

https://apiloterias.com.br/app export default class LotteryApi { getLottery = async (lottery) => { try { const { data } = await request.get('/resultado', { params: { loteria: lottery } }); return data; } catch (error) { console.error(error); } }; } this way I call the endpoint I want and return the data

Brody•2y ago

it would significantly help if i could see the repo

lucaszdevmmyers616OP•2y ago

Why??? it's only this I send you, there is nothing more it's only the call I only call: lotteryApi.getLottery(...)

Brody•2y ago

its not much to go off of show me a screenshot of the error?

lucaszdevmmyers616OP•2y ago

Brody•2y ago

likely wrong syntax

const instance = axios.create({
  baseURL: 'https://some-domain.com/api/',
  timeout: 1000,
  headers: {'X-Custom-Header': 'foobar'}
});

const instance = axios.create({
  baseURL: 'https://some-domain.com/api/',
  timeout: 1000,
  headers: {'X-Custom-Header': 'foobar'}
});

https://www.npmjs.com/package/axios#user-content-creating-an-instance

lucaszdevmmyers616OP•2y ago

No, in localhost works fine

Brody•2y ago

try with the correct syntax

lucaszdevmmyers616OP•2y ago

It's not this, I change the Promise I have and worked, I don't know what the error is in Axios, but when I redeploy worked, the axios is right, this headers is custom there is no problem with my axios call, but thank you so much

Brody•2y ago

okay so it was a code issue either way glad its working now!

lucaszdevmmyers616OP•2y ago

Yes, is something about the Promise, in the catch of the Promise I wasn't using the res.status...

Brody•2y ago

mmm mixing await with promises yummy wrapped in a big try / catch block

Finn•2y ago

await is a keyword that resolved promises though

.then .catch is not good though

Brody•2y ago

Finn you know what I mean

Finn•2y ago

i do and here are some links around handling promises if you want @Lucas Lima https://www.youtube.com/watch?v=ITogH7lJTyE https://trytm.vercel.app/

lucaszdevmmyers616OP•2y ago

not work the promises is to the map await until end to then return if I do without promises the array is send empty

Finn•2y ago

can you paste the code i can format it so it works (discord formatting so it will be slightly ugly looking ) ( i asume the issue is your resolving the promises then trying to send a request back, but the request is closed )

lucaszdevmmyers616OP•2y ago

try { const lotteriesArray = []; const promises = lotteries.map(async (lottery, index) => { const response = await lotteryApi.getLottery(lottery); lotteriesArray[index] = { lottery_name: response.nome, amount: response.valor_estimado_proximo_concurso, color: lotteryColors[index], date: response.data_concurso, tender_number: response.numero_concurso, description: lotteryDescription[index] }; }); Promise.all(promises).then(() => { res.status(200).json({ status: 200, lotteries: lotteriesArray }); }).catch(error => { res.status(500).json({ error: "Server error, please try again later." }); }); } catch (error) { res.status(500).json({ error: "Server error, please try again later." }); } the all code

Finn•2y ago

try {
        const promises = lotteries.map(async (lottery, index) => {
            const response = await lotteryApi.getLottery(lottery);

             return {
                lottery_name: response.nome,
                amount: response.valor_estimado_proximo_concurso,
                color: lotteryColors[index],
                date: response.data_concurso,
                tender_number: response.numero_concurso,
                description: lotteryDescription[index]
            };
        });

        const lotteries = await Promise.all(promises)
        res.json({
                status: 200,
                lotteries: lotteries
            })
    
    } catch (error) {
        res.status(500).json({
            error: "Server error, please try again later."
        });
    }

try {
        const promises = lotteries.map(async (lottery, index) => {
            const response = await lotteryApi.getLottery(lottery);

             return {
                lottery_name: response.nome,
                amount: response.valor_estimado_proximo_concurso,
                color: lotteryColors[index],
                date: response.data_concurso,
                tender_number: response.numero_concurso,
                description: lotteryDescription[index]
            };
        });

        const lotteries = await Promise.all(promises)
        res.json({
                status: 200,
                lotteries: lotteries
            })
    
    } catch (error) {
        res.status(500).json({
            error: "Server error, please try again later."
        });
    }

somthing like that? oh wait 1 sec that worke @Lucas Lima i must admit ive never used promise.all

Brody•2y ago

isn't there a way to do error handling without encapsulating everything in a try block?

Finn•2y ago

Brody•2y ago

Example, because I would like to know too

Finn•2y ago

using or the like

export const to = async <T>(
   promise: Promise<T>,
): Promise<[T, null] | [null, Error]> => {
   try {
      return [await promise, null];
   } catch (e) {
       return [null, e instanceof Error ? e new Error(String(e))];    
   }
};

export const to = async <T>(
   promise: Promise<T>,
): Promise<[T, null] | [null, Error]> => {
   try {
      return [await promise, null];
   } catch (e) {
       return [null, e instanceof Error ? e new Error(String(e))];    
   }
};

~~( altho i would not have that last line )~~ fixed

Brody•2y ago

That's still try catch, or is that just the extent of JavaScript's error handling?

Finn•2y ago

nah the idea is you wrap the function that throws with to and yes this is the extent. like

const [res, error] = await to(
    fetch("/myThing")
         .then(async r => zodSchema.parse(await r.json())
)

if (error) return console.log("error yes")

... do more things

const [res, error] = await to(
    fetch("/myThing")
         .then(async r => zodSchema.parse(await r.json())
)

if (error) return console.log("error yes")

... do more things

error handling in ts is BAD

Brody•2y ago

Hey that look like Go

Finn•2y ago

p much. and thats my goto solution

Brody•2y ago

I like that example

Finn•2y ago

which example

Brody•2y ago

The one that looks like Go

Finn•2y ago

this?

Brody•2y ago

Finn•2y ago

@Lucas Lima let us know if it worked or not when you are back ah yea that

Brody•2y ago

I will yoink for later use, thank you

Finn•2y ago

nw. make sure you use zod aswell!

Brody•2y ago

I don't do typescript

Finn•2y ago

oh and it requires ts 4.6 > to get the inference union working properly

Brody•2y ago

Typescript is for people with wrinkly brains

Finn•2y ago

( thats a compliment lol ) did you mean that

Brody•2y ago

Yes, I'm smooth brain so everything I do is vanilla

Finn•2y ago

Brody•2y ago

everything

Gaming

Programming

AxiosError: connect ECONNREFUSED 127.0.0.1:80