Service URL: saascope-api-production.up.railway.app

Facts:

  • Service shows Online

  • Public Networking enabled

  • Target Port = 8080

  • Domain resolves in DNSChecker

  • Generated multiple new Railway domains with same result

  • No HTTP logs appear when hitting public domain

  • Inside container:

  • Express server listening on 0.0.0.0:8080

  • Public domain returns "This site can't be reached"

This suggests traffic is not reaching the service despite successful deployment and healthy local connectivity inside the container.

Could you investigate the public routing/networking for this service?

1 Replies

solved


Welcome!

Sign in to your Railway account to join the conversation.

Loading...