Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Re-Deploy failed

See original GitHub issue

On first deploy, everything works like expected. But on the second deploy i get an error “Error: Unable to create basepath mapping.”

I did a little debugging and console logged the whole error.

{ ConflictException: Base path already exists for this domain name
    at Object.extractError (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/protocol/json.js:51:27)
    at Request.extractError (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/protocol/rest_json.js:52:8)
    at Request.callListeners (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (/usr/local/lib/node_modules/serverless/node_modules/aws-sdk/lib/event_listeners.js:299:13)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1055:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)
  message: 'Base path already exists for this domain name',
  code: 'ConflictException',
  time: 2019-02-07T16:38:04.412Z,
  requestId: 'bda550d2-2af6-11e9-ae36-adc5f98f436f',
  statusCode: 409,
  retryable: false,
  retryDelay: 63.98059250701831 }

How to deploy a new version of my code ?

Issue Analytics

State:
Created 5 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

8reactions

captainsiddcommented, Feb 14, 2019

@alexandrecanuto Not a problem! If you go to API Gateway, scroll down on the left to Custom Domain Names, then select Show Basepath Mappings, you should see something that looks like this:

screen shot 2019-02-14 at 8 58 45 am

Clicking the trash can should delete your basepath mapping manually.

Hope that helps.

4reactions

daneholmbergcommented, Oct 21, 2019

Is there any way to fix this with no downtime? So that we don’t have to delete the base path?

Top Results From Across the Web

Redeploy the Failed NSX-T Manager Node - VMware Docs

You deploy a new NSX-T Manager instance by using the configuration of the failed node.

When I try to redeploy a failed release I'm unable to see the ...

Normally there's a scrollbar so that you can scroll past the artifacts list and get the bottom where the Deploy button is located....

Redeploy Windows virtual machines in Azure - Microsoft Learn

This article shows you how to redeploy a VM using Azure PowerShell or the Azure portal. If the VM is stuck in a...

Mule maven plugin deploy and redeploy fails

The application works properly in local environment, but when the application is deployed to CloudHub using the mule-maven-plugin appears the following error ( ......

azure web app service - Redeploy failed git deployment

Occasionally, for whatever reason, when I deploy a commit via azure websites local git repo, it cannot find one of our remote repos...