Built Backstage in a docker container in WSL; Can’t connect to localhost:3000

[fervent path]

When I attempt to connect to localhost:3000, I get an err_empty_response message from the browser

Nothing shows up in server logs either.

If I try to connect to localhost:7007, entries appear in the logs, but I get a 404 error in the browser.

I would appreciate any advice you could give. Thank you in advance.

[edgy crater]

just to double-check, the app.baseUrl is set to http://localhot:3000?

[fervent path]

Yes

App Yaml:

app:
title: Scaffolded Backstage App
baseUrl: http://localhost:3000

organization:
name: My Company

backend:

Used for enabling authentication, secret is shared by all backend plugins

See https://backstage.io/docs/auth/service-to-service-auth for

information on the format

auth:

keys:

- secret: ${BACKEND_SECRET}

baseUrl: http://localhost:7007
listen:
port: 7007
# Uncomment the following host directive to bind to specific interfaces
# host: 127.0.0.1
csp:
connect-src: ["'self'", 'http:', 'https:']
# Content-Security-Policy directives follow the Helmet format: https://helmetjs.github.io/#reference
# Default Helmet Content-Security-Policy values can be removed by setting the key to false
cors:
origin: http://localhost:3000
methods: [GET, HEAD, PATCH, POST, PUT, DELETE]
credentials: true

This is for local development only, it is not recommended to use this in production

The production database configuration is stored in app-config.production.yaml

database:
client: better-sqlite3
connection: ':memory:'

workingDirectory: /tmp # Use this to configure a working directory for the scaffolder, defaults to the OS temp-dir

integrations:
github:
- host: github.com
# This is a Personal Access Token or PAT from GitHub. You can find out how to generate this token, and more information
# about setting up the GitHub integration here: https://backstage.io/docs/getting-started/configuration#setting-up-a-github-integration
token: ${GITHUB_TOKEN}
### Example for how to add your GitHub Enterprise instance using the API:
# - host: ghe.example.net
# apiBaseUrl: https://ghe.example.net/api/v3
# token: ${GHE_TOKEN}

proxy:

Example for how to add a proxy endpoint for the frontend.

A typical reason to do this is to handle HTTPS and CORS for internal services.

'/test':

target: 'https://example.com'

changeOrigin: true

Reference documentation http://backstage.io/docs/features/techdocs/configuration

Note: After experimenting with basic setup, use CI/CD to generate docs

and an external cloud storage when deploying TechDocs for production use-case.

https://backstage.io/docs/features/techdocs/how-to-guides#how-to-migrate-from-techdocs-basic-to-recommended-deployment-approach

techdocs:
builder: 'local' # Alternatives - 'external'
generator:
runIn: 'docker' # Alternatives - 'local'
publisher:
type: 'local' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.

auth:

see https://backstage.io/docs/auth/ to learn about auth providers

providers: {}

scaffolder:

see https://backstage.io/docs/features/software-templates/configuration for software template options