Hey @ramoth123 this behavior often means that your project isn’t listening on the port that Glitch opens (typically port 3000, but it changes under some circumstances - process.env.PORT will always reflect the current one as long as you’re not overriding it). This sample express config shows one way of handling that.
If that’s not the case in your project can you please share the project name and someone will take a closer look?