repl_setup

Add allowedHosts: true to the server section of vite.config.ts, bind the host to 0.0.0.0, and set the port to 5000. Restart the workflow after changing the config so the Replit proxy can reach your dev server.

The most common cause is missing host configuration that blocks the Replit proxy. Verify the dev server allows all hosts, confirm the workflow is running and restarted, then check console logs for errors before investigating cache issues.

Run env | grep DOMAIN in the shell to get the public Replit domain and use it instead of localhost in your API calls. You can also configure a proxy entry in vite.config.ts that forwards /api requests to your backend port.

Frontend servers must bind to 0.0.0.0 on port 5000, and nothing else should occupy that port. Backend services should run on different ports while the frontend remains the public entry point.

No, Docker, virtual environments, and containerization are not supported because Replit uses a Nix environment without nested virtualization. Install dependencies directly through the environment's package management instead.

Skip it for non-web applications like CLI tools and scripts, when the application already works correctly, or for deployment and publishing issues, which are handled by a separate deployment skill.