An error has occured | Backstage | Page 1

silver lark Jan 22, 2024, 5:12 PM

#

The Redirect URI included is not valid on Gitlab(on an enterprise GitLab as well as on gitlab.com). I get this on https://alb-dns where the backend is running on https://alb-dns:8443. This setup is run on AWS and my client has restrictions on running EC2 in public subnet. I eventually want to take this setup to ECS Fargate or EKS(If this is successful). Any help or pointers would be greatly appreciated.

opal tulip Jan 23, 2024, 2:17 AM

#

Hi @silver lark , maybe this article would be helpful, https://roadie.io/blog/backstage-fargate-up-and-running/

Deploying Backstage application to AWS ECS Fargate | Roadie

Hosted, managed, enterprise Backstage

silver lark Jan 23, 2024, 5:08 AM

#

Hey @opal tulip , went through this article when I started off exploring Backstage. This document helped a lot to get a start but my POC Architecture is little different than what is given here. as I said the company where I work doesn't allow EC2 running on Public subnet so we need to front whatever apps are running on EC2 with ALBs. Thanks for this!

opal tulip Jan 23, 2024, 7:27 AM

#

Hi @silver lark , I am currently using an ALB to deploy our instance. May I check what issue are you facing ?

silver lark Jan 23, 2024, 11:01 AM

#

Hi @opal tulip , would you be able to have a look at this bug >> https://github.com/backstage/backstage/issues/22460 which I created in the Backstage Project. There I have mentioned all the information in the context of the issue I am facing.
Thank you

GitHub

🐛 Bug Report: Backstage application fails to reach backend when usi...

📜 Description I am trying out Backstage on an EC2 instance which is fronted by an AWS ALB. the backend is running on port 7007 whereas the frontend running on 3000. the ALB listener is configured o...

opal tulip Jan 23, 2024, 3:26 PM

#

Hi @silver lark , may I check why is your backend connecting to 8443, instead of 7007. Because your error message says that the callback URL, is looking for port 7007. Please do check on that.

#

I am not sure if that is the reason for the issue. But you could just try with the instance running and listening on the port 7007. Also, the security groups to allow incoming traffic on port 7007.

silver lark Jan 23, 2024, 3:52 PM

#

Hi @opal tulip , 8443 is mapped to 7007 port on ALB 🙂

#

so the backend is on EC2_PRIVATE_IP:7007 but its being fronted by 8443

opal tulip Jan 24, 2024, 1:40 AM

#

Hi @silver lark, I see. But then the app_config.yaml file is still pointing towards the port 3000 and 7007, which isn't required for deployment stage with the ALB_DNS. All three URL's App_Base_Url, Backend_base_url and CORS_origin should be the same. In your case, the ALB_DNS.

#An error has occured