serverless-domain-manager: Error: Unable to get BasePathMappings for domain.com

Setting the string to empty as indicated in the examples, causes the the error.

Error: Unable to get BasePathMappings for domain.com

Also, no record is created in Route53

  customDomain:
    domainName: dev.domain.com
    basePath: ''
    certificateName: '*.domain.com'
    stage: ${self:provider.stage}
    createRoute53Record: true

Missing something?

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 17
Comments: 28 (5 by maintainers)

Most upvoted comments

you can also get this error if you do not call sls create_domain

+72

ryderjgillen on Mar 20, 2019

Make sure you run sls create_domain before running sls deploy. That did the trick for me.

+26

felimartina on Apr 25, 2019

Yeah, I just started doing that and it seems to fix the problem.

Is that how it’s meant to work? I didn’t see anything about that in the docs.

Edit: Just re-read the docs. It’s there. 🤦‍♂️

mattdell on Apr 26, 2019

I found that I had to set endpointType (default is ‘edge’, I needed ‘regional’) to solve this error.

seba-i on Jun 23, 2019

You should add endpointType, like this:

    domainName: dev.domain.com
    basePath: ''
    certificateName: '*.domain.com'
    stage: ${self:provider.stage}
    createRoute53Record: true
    endpointType: regional

Then: sls create_domain sls deploy -v

cmanzur on Jan 31, 2020

Having the same problem! Let me know if you were able to sort it out.

felimartina on Mar 12, 2019

Me to i had the same problem. The problem was that i used another AWS account. Be sure you use your right aws account . Verify it here: C:/Users/USER1/.aws/credentials

abdodeve on Jan 7, 2020

It’s very confusing that I had to create first the domain, and then deploy. In my opinion this should be at least logged in the output of the failing create_domain.

sscarduzio on Dec 8, 2019

@captainsidd 😕 , still end up with Error: Unable to get BasePathMappings; simply trying to point route 53 A record alias to the cloudfront distribution.createRoute53Record: true doesnt seem to change anything in the dns. sls create_domain by itself yields Error: Failed to create custom domain

promediacorp on Mar 22, 2019

Hi everyone! We rolled out better debug messages in 3.2.1 that should help identify why you’re experiencing this issue (incorrect permissions or not finding the domain as a result of not running sls create_domain as @rgillen stated). Let us know what’s going on!

captainsidd on Mar 22, 2019