Failed to Load Resource error

Hey everyone! I'm new to Open Wasp but have a background in coding (especially with Python). I'm currently building my first app using the Open SaaS template and trying to deploy it on Fly.io.

I'm running into a couple of issues:

1. Login Option Missing on Deployed App
The login option works fine on localhost, but when I deploy to Fly.io, it doesn't appear. In the browser console, I'm seeing repeated errors like this:

   Failed to load resource: net::ERR_NAME_NOT_RESOLVED (502 and 503 errors)
   https://[my-app-server].fly.dev/auth/me

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

   Failed to load resource: net::ERR_NAME_NOT_RESOLVED (502 and 503 errors)
   https://[my-app-server].fly.dev/auth/me

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

It seems like it's not resolving the server endpoint correctly on the deployed site. Any ideas on what might be going wrong?

2. Network Error with Custom Operation
I created a

wasp/client/operations

wasp/client/operations

operation that makes a request to a Flask API. This works fine locally and even when calling the Fly.io Flask API from localhost. But on the deployed app, I get a generic "Network Error." Not sure how to debug this any tips?

Would really appreciate any help or suggestions!

Failed to Load Resource error

   Failed to load resource: net::ERR_NAME_NOT_RESOLVED (502 and 503 errors)
   https://[my-app-server].fly.dev/auth/me

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

   Failed to load resource: net::ERR_NAME_NOT_RESOLVED (502 and 503 errors)
   https://[my-app-server].fly.dev/auth/me

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

It seems like it's not resolving the server endpoint correctly on the deployed site. Any ideas on what might be going wrong?

2. Network Error with Custom Operation
I created a

wasp/client/operations

wasp/client/operations

Failed to Load Resource error

Failed to Load Resource error

Continue the conversation

Wasp

Continue the conversation

Wasp

Similar Threads