While building our project, we ran into a key hurdle during deployment.

We were able to deploy the frontend successfully, but couldn’t deploy the backend because the platform required a paid plan for that. So, we came up with a workaround — we deployed just the frontend and ran the backend server locally on our system.

But this setup caused a problem: when we opened the deployed frontend, it couldn’t connect to the backend since it was running on localhost. And since the frontend was live on the internet, it had no way of talking to something that was only running on our local machine.

This meant that features depending on the backend didn’t work on the deployed version. It was a learning experience for us — especially about the need to plan full-stack deployment early on, and to look into free backend hosting options or environment-specific configuration settings to avoid such issues.