Open rosiech opened 4 years ago
I'm having the same issue.
What I've noticed is that Access-Control-Allow-Origin
still points to the old CloudFront URL, which causes failure of CORS preflights.
You can try to export the OpenAPI definition of the backend API (should be called serverlessrepo-api-gateway-dev-portal-backend-api
by default) from API Gateway and check the value of method.response.header.Access-Control-Allow-Origin
.
Added: Actually I've just solved my issue by re-deploying my serverlessrepo-api-gateway-dev-portal-backend-api
...
Aw man....wish I could shake your hand - worked for me too. Consider this a virtual one (and the way the world is at the minute, virtual ones are probably better!) THANKS!
I'm having issues updating the portal with a subdomain. Everything is good before trying to update:![image](https://user-images.githubusercontent.com/34463708/76469680-bcc12f00-63bc-11ea-8fdb-c5858eb8f59c.png)
update was done and route53 was updated:
when the base host was updated with the NS, it looks OK until I log in.
When I log in the api isn't present.![image](https://user-images.githubusercontent.com/34463708/76469913-4ffa6480-63bd-11ea-906a-5588305b96a2.png)
Tried: updating the api with redoing the usage plan redeploying the api using another user (and making them admin) also tried uploading a swagger file and it wouldn't upload?
Help would be appreciated!