After deployment having some URL callbacks fail for nextJS due to request coming from localhost?

[jay2jp]

Hello, I recently completed the whole procedure for this and I am having a strange issue. I am currently using Supabase Auth with a next-JS project on amplify and after switching off of custom domains and routing everything through cloudfront I can access the application! However, when using a Oauth provider such as Google or Microsoft the callback gets sent properly. It all looks proper on the network logs within the browser and on supabase however when I monitor the logs from the Amplify hosted compute logs side it seems that the request is coming from localhost:3000 and contains no query params. Considering everything else works and the host of requests is set from environment variables that are being accessed before this step I am certain this is not user error of Oauth on my end. would it be possible for the custom origin to be making it appear to amplify as this request is coming from localhost? Does this deployment not work for applications that require Server Side Rendering?

This is not the issue of the callback referring to local host either see below for network logs.

[theolrvlv]

Hi, you can check this issue I had some months ago, I let you look at it and see if it can help you :
#9

I achieve to use this solution for my SSR website on amplify so maybe you misconfigure something around cloudfront ?