Error in apigateway console cant open Authorizers page

0

Hello

I have a problem with api gateway console. When i access Authorizers page, my authorizator not appears. I have a custom lambda authorizer working fine. When i click in Create new authorizer nothing happens. Looking into chrome console i see this error:

Error

vendors.js:383 Uncaught TypeError: Cannot read properties of null (reading 'nextSibling') at u.getHostNode (vendors.js:383:2231985) at Object.getHostNode (vendors.js:27:90489) at Object.updateChildren (vendors.js:383:2243871) at J._reconcilerUpdateChildren (vendors.js:383:2244611) at J._updateChildren (vendors.js:383:2245572) at J.updateChildren (vendors.js:383:2245470) at J._updateDOMChildren (vendors.js:383:2262949) at J.updateComponent (vendors.js:383:2261173) at J.receiveComponent (vendors.js:383:2260726) at Object.receiveComponent (vendors.js:27:90732) getHostNode @ vendors.js:383 getHostNode @ vendors.js:27 updateChildren @ vendors.js:383 _reconcilerUpdateChildren @ vendors.js:383 _updateChildren @ vendors.js:383 updateChildren @ vendors.js:383 _updateDOMChildren @ vendors.js:383 updateComponent @ vendors.js:383 receiveComponent @ vendors.js:383 receiveComponent @ vendors.js:27 _updateRenderedComponent @ vendors.js:383 _performComponentUpdate @ vendors.js:383 updateComponent @ vendors.js:383 performUpdateIfNecessary @ vendors.js:383 performUpdateIfNecessary @ vendors.js:27 y @ vendors.js:19 perform @ vendors.js:34 perform @ vendors.js:34 perform @ vendors.js:19 w @ vendors.js:19 closeAll @ vendors.js:34 perform @ vendors.js:34 batchedUpdates @ vendors.js:383 e @ vendors.js:19 a @ vendors.js:84 enqueueSetState @ vendors.js:84 a.setState @ vendors.js:98 a.openCreatePanel @ 4.js:1 wrappedCb @ vendors.js:383 t @ vendors.js:385 e.__fireEvent @ vendors.js:385 click @ vendors.js:387 onclick @ vendors.js:387 (anonymous) @ vendors.js:387 vendors.js:368 POST https://telemetry.cell-0.us-east-1.prod.tangerinebox.console.aws.a2z.com/telemetry 400

1 Answer
0

your browser might bring this issue, because you seem to get HTTP 400 error. so try this via aws cli.

Here is a document for the trial.

https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-lambda-authorizer.html

profile pictureAWS
nemf
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions