2 months ago
When I initiate a session, I get "Network Error". Everything appears OK. How can I see where the "network error" originates? My session ID is: Session 4337448d-6cad-4a7e-a0a5-6ac9edf11677.
Pinned Solution
a month ago
I'd check your codebase for errors. I uploaded an image, and your application was able to call Supabase's API successfully (inspected via network tab in devtools). I wasn't able to find any API errors in the network tab.
5 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Can you give a bit more context? What is this "session" you're trying to start? What are you hosting?
2 months ago
When you say App are you perhaps trying to start a Cloud Agent session via railway ca, railway code, or the dashboard which ? And what else do you see when the network error appears?
0x5b62656e5d
Can you give a bit more context? What is this "session" you're trying to start? What are you hosting?
a month ago
Thanks for your help. I don't know enough to explain it better. Here is the URL: https://snapnfind-api-development.up.railway.app/ . Choose a media file and click submit. You'll get a "Network Error" in the top box.
tired-21
When you say App are you perhaps trying to start a Cloud Agent session via railway ca, railway code, or the dashboard which ? And what else do you see when the network error appears?
a month ago
Thanks for your help. I have an app that was developed by someone else. Here is the URL: https://snapnfind-api-development.up.railway.app/ . Choose a media file and click submit. You'll get a "Network Error" in the top box.
quinnguru
Thanks for your help. I have an app that was developed by someone else. Here is the URL: https://snapnfind-api-development.up.railway.app/ . Choose a media file and click submit. You'll get a "Network Error" in the top box.
a month ago
I'd check your codebase for errors. I uploaded an image, and your application was able to call Supabase's API successfully (inspected via network tab in devtools). I wasn't able to find any API errors in the network tab.
Status changed to Solved 0x5b62656e5d • 20 days ago