Trouble SSH'ing into Fly.io Frontend App – "user does not exist" & Auth Errors
Hey folks! I'm running into an issue trying to SSH into my frontend app deployed on Fly.io.
And when I run
flyctl ssh console, I get:
error connecting to SSH server: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
When I check the logs, I see:
ERROR user does not exist user=root
Weird thing is — I can SSH into my other apps on Fly just fine (like the backend or a standalone Python service). It's only the frontend app giving me this trouble.
Has anyone run into this before? Could it be something with the Docker image or missing root user?
Appreciate any help 🙏4 Replies
Hi @Orestis. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I don't have specific information about SSH issues with frontend apps on Fly.io in the Wasp ecosystem. The documents mention using
flyctl ssh console as a useful command for Wasp deployments, but don't address the specific error you're encountering.
When deploying Wasp apps to Fly.io, the frontend (client) is typically deployed as a static site, while the backend (server) is deployed as a Docker container. This architectural difference might explain why you can SSH into your backend but not your frontend.
From the Wasp documentation:
"We suggest using Netlify for your client, but you can use any static hosting provider." Deploying ManuallyThis suggests that the frontend is typically not designed to be SSH-able in the same way as the backend, as it's usually just static files. I'd recommend: 1. Checking if your frontend is actually deployed as a container rather than static files 2. Reviewing your Dockerfile for the frontend to ensure it has the proper user setup 3. Checking Fly.io's documentation specifically about SSH access to static sites If you need to troubleshoot your frontend, you might want to look at logs using
flyctl logs instead of trying to SSH into it.
Is there a specific reason you need SSH access to your frontend deployment?
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Orestis, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hey, I think probably they'll be able to help you better over at the Fly support forums. I did look for peole who might have had similar issues (1, 2, 3), it seems most of them got their issue resolved by waiting a couple of minutes and/or restarting their app.
Ok thank you, I will try again!
Wohooo @Orestis, you just became a Waspeteer level 1!