Workspace creation timeout
Describe the bug Started a simple workspace (https://github.com/docker/awesome-compose) using a remote profile (mac laptop profile setup to talk to linux desktop) and it failed with a timeout.
❯ daytona create compose -r https://github.com/docker/awesome-compose
WORKSPACE CREATION
┌───────────────────────────────────────────────────────────────────────────────┐
│ │
│ Workspace creation request submitted │
│ Creating workspace │
│ Initializing network │
│ Network initialized │
│ Creating project awesome-compose │
│ Pulling image... │
│ │
└───────────────────────────────────────────────────────────────────────────────┘
FATA[0064] <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
/html>
If you check the list, it appears to be there but isn't running.
❯ daytona list
WORKSPACE REPOSITORY BRANCH TARGET
compose docker/awesome-compose local
~
❯ daytona ssh
FATA[0003] lookup MTc4NDMzNDAxMDk1OTQ1Mzk0Njk: no such host
Connection closed by UNKNOWN port 65535
FATA[0005] exit status 255
To Reproduce Steps to reproduce the behavior:
- Create daytona server with API key
- Add profile for server with API remotely
- Create a workspace
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
- OS: Mac 14.4 and Ubuntu 22.04
- Daytona Version: v0.12.1
Additional context Works fine if you run the create on the Linux box.
@metcalfc can you check if the issue occurs on a fresh installation of Daytona?
You can run daytona purge on the remote machine, install the binary again and run the server and connect to it from your local machine.
Seems the issue is not because of the remote server.
We'll investigate more and get back to you. This might be an issue on our US FRP server.
Sounds good. Just info wise: Both were fresh installs. The Linux server was fresh all the way to the os.
We've tracked down the issue to a HTTP request timeout that's happening during the workspace creation request.
I'll provider more updates once we get closer to a solution.
Resolved the issue on our FRP and Nginx. Requests should now have a 1-hour timeout.