Set Custom Domains Through Seed


#1

Link to chapter - https://serverless-stack.com/chapters/set-custom-domains-through-seed.html


#2

Hello @jayair I have been working in this tutorial and in this point I get the following error:

An error ocurred while trying to update the custom domain. Please refresh the pages and try again. You can also contact us if you need any help.

In the first part of the tutorial I buy the domain my-serverless-app.uk and I had problems with it. I buy the domain .uk because It is cheaper that .com domain but
I am beginning to believe that It was a bad idea.

Can you recommend to buy a new .com domain and configure again?


#3

I think we were helping you out with the error. But the error is happening because the Certificate Manager is unable to verify that you own the domain.

Btw, did you purchase the domain through Route 53?


#4

Hello @jayair, I buy the domain by frenom.com… I believe It was another bad idea… I go to apply the process again through Route 53. I hope come with news soon.


#5

I buy now the domain yourbiblenotes.com and the site is working except the upload of file. The behaviour is the same I posted in https://discourse.serverless-stack.com/t/comments-for-upload-a-file-to-s3/123/46


#6

Can you tell me what the issue is? Or post it in that thread?


#7

The error says: NetworkingError: Network Failure when I try upload a file. In the console I receive the following errors and warnings:

Access to XMLHttpRequest at ‘https://notes-app-uploads-jdccr.s3.us-east-2.amazonaws.com/private/us-east-2%3A636d8661-1573-42e5-aa8b-83f6854c666f/1552336944885-Welky.txt’ from origin ‘https://yourbiblenotes.com’ 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.

Cross-Origin Read Blocking (CORB) blocked cross-origin response https://notes-app-uploads-jdccr.s3.us-east-2.amazonaws.com/private/us-east-2%3A636d8661-1573-42e5-aa8b-83f6854c666f/1552336944885-Welky.txt with MIME type application/xml. See https://www.chromestatus.com/feature/5629709824032768 for more details.


#8

You need to make sure the CORS settings from this chapter are set correctly.