Route not found when in production #368
-
Hello, I am using supabase-js for the API connection. On my local machine using docker or node server I am able to retrieve all the data correctly but when I try on my production server I get this JSON: {
"error": {
"message": "no Route matched with those values"
},
"data": null,
"status": 404,
"statusText": "Not Found",
"body": null
} Is this a known problem? The API is online and the requests are being made on the correct API. Can someone give me some light, please? I am using Express for powering the API. Here is the "dependencies": {
"@apidevtools/swagger-parser": "^10.0.2",
"@sendgrid/mail": "^6.5.4",
"@supabase/supabase-js": "^1.0.7",
"body-parser": "^1.19.0",
"consign": "^0.1.6",
"cors": "^2.8.5",
"dotenv": "^8.1.0",
"express": "^4.17.1",
"mongoose": "^5.7.1",
"morgan": "^1.10.0",
"request": "^2.88.0",
"socket.io": "^2.2.0",
"swagger-jsdoc": "^6.0.0-rc.3",
"swagger-parser": "^10.0.2",
"swagger-ui-express": "^4.1.5",
"uuid": "^8.3.2"
} |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Hey @jvbraganca,
What |
Beta Was this translation helpful? Give feedback.
-
@steve-chavez with curl I was able to retrieve the data. Any idea why I am not with express? The request: curl 'https://tbqtyripmdyrulzpwzvb.supabase.co/rest/v1/chats?select=*' \
-H "apikey: SUPABASE_KEY" \
-H "Authorization: Bearer SUPABASE_KEY"
The response: [
{
"id": "bc5cc363-5d06-4820-8350-5f8dba146e11",
"title": "Hello, World!",
"from": "5efaaaa76dd03a016c68236e",
"to": "21232f297a57a5a743894a0e4a801fc3",
"updated_at": "2020-12-09T15:57:19.50431+00:00",
"created_at": "2020-12-09T15:57:19.50431+00:00",
"country": "BR"
}
] UPDATE: Wait I copied the URL from the Supabase page. UPDATE 2: Checked again my URL and I was getting this error because of an extra Feeling blind as hell! Thank you, guys! |
Beta Was this translation helpful? Give feedback.
@steve-chavez with curl I was able to retrieve the data. Any idea why I am not with express?
The request:
UPDATE: Wait I copied the URL from the Supabase page.
UPDATE 2: Checked again my URL and I was getting this error be…