Question: Why status is "pending" for setting up a custom domain. Both for domain and "www" redirect, but deploy work?
From the side of domain provider all is ok
Related
After deploying a Next.js app on AWS Amplify and using a rewrite to an external server, when inspecting the request headers, the User Agent header is Amazon CloudFront instead of the user's user agent.
When deploying the same Next.js app on Vercel, the user agent reflects the actual user's user agent, which is the expected behaviour.
Does anyone know how to fix this issue on AWS Amplify?
I am currently trying to build an app that will be run by each client in their own custom server with their custom hostname and the allowed authenticated users change for each client. Therefore, I need to create a user pool for each client, which will redirect them to their custom hostname after a successful login. However, the redirect URL is in the source code in _app.js and once the app builds, this can't be changed. I tried setting this in an environment variable that changes for each client, but I can't read the environment variable from the app once it's built, and I can't pass the redirect address before build-time, because that would imply changing the source code for each client. Is there any way to define the redirect URL at runtime so it adapts to the client's hostname?
I hosted a website in firebase hosting and connected a custom domain, the domain is connected properly as you can see in the screenshot.
firebase hosting screenshot
The problem is if someone for the first time in their browsing session writes http://plucreo.com it does not get redirect to https://plucreo.com and the connection gets timed out. This does not happen with the default domain http://plucreo.web.app it redirects to https:// one correctly.
But, if you manually type https://plucreo.com in address bar, for the current browsing session http://plucreo.com starts correctly redirecting to https:// one.
How to fix this redirecting issue?
I have a chrome extension using Firebase that is running for years now.
Recently I have activated the 'Strict Mode for Redirect URI' in the Facebook Login option, and the Login is not working anymore.
I've copied the URI givent by Firebase in the 'Valid OAuth Redirect URIs' : https://safestkeys.firebaseapp.com/__/auth/handler
But this link doesn't pass the 'Redirect URI Validator' provided by Facebook...
When I try to log I get the following error messages:
Blocked URL: Redirection failed because the redirected URI is not trusted in
the application's OAuth Client settings. Make sure that the OAuth Client and Web ID are enabled and add the domains for all your applications to the list of allowed URIs.
Unable to load this URL: The domain of this URL is not registered in those of the application. To import this URL, add all the domains and subdomains of your application to the Domains field of the application settings.
I've also realized that even with these errors, the login actually works...
I'm running a Wordpress multisite instance configured with subdomains.
Developing locally no problem so far.
Once deployed I found out an auto redirect from domain.com to www.domain.com imposed by the system admins managing the servers.
But with this redirect it seems I cannot access the network admin panel anymore.
I log in www.domain.com or www.domain.fr or any configured mapped domain as admin
Once inside I get the dashboard for the site I logged in
I go on "network administration" and wordpress redirect me to the network domain aka domain.com
The autoredirect push me back again to www.domain.com and I get previous domain dashboard once more
Is there any way to access the network dashboard within the subdomains?