-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daytona server - control is not running #664
Comments
@vedranjukic , please suggest |
@kabir-baba thanks for such a detailed issue. Can you please start the server in the foreground with |
@Tpuljak , thanks for a fast response
|
@kabir-baba seems the issue is that the Headscale (Tailscale) server can not start and connect properly. Most of the time, this means that you either have a firewall that's blocking it or your Wifi router is blocking connections to our FRP (reverse proxy) server. Can you check if you have firewalls enabled that might be blocking this? |
@Tpuljak disabled firewall , still the same
|
@kabir-baba okay, one potential problem eliminated 😄 Are you maybe using a VPN? If not, is there a chance you can try another network? Asking because we had a situation when a conferences WiFi connection was blocking reverse proxies. |
@Tpuljak , but thats so strange , everytime I connect laptop to different WiFi networks , always there will be an issue with daytona What could be the workaround as checking reverse proxy rules in very network is a thing ....hope u understand :) Also can you explain why there is a dependency on FRP ? |
@kabir-baba I understand your point and we're still exploring ways of detecting these specific networking errors and providing workarounds. The FRP connection is required to allow workspaces to communicate with the Daytona Server and register on its Tailscale network. Additionally, it allows you to configure remote profiles (with We have #625 opened which will tackle removing the strict dependency to FRP and allow users to directly communicate with the Server via its IP address. In the meantime, the best thing I could suggest is that, if possible, you run Daytona on a remote machine that is inside a network that allows reverse proxies, you create a new api key with |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 14 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Describe the bug
When attempting to install and start the Daytona server using the provided installation script and commands, the server fails to start and returns a "connection refused" error.
To Reproduce
Steps to reproduce the behavior:
Steps to Reproduce:
Expected behavior
The Daytona server fails to start and returns the following error: FATA[0035] Get "http://localhost:3986/health": dial tcp 127.0.0.1:3986: connect: connection refused
Additionally, attempting to view the Daytona server logs returns the error: FATA[0000] active profile not found
Attempting to serve Daytona returns the error: FATA[0011] control is not running
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Docker version
The text was updated successfully, but these errors were encountered: