Skip to content
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 ignores no_proxy env variable #1692

Open
bafzachris opened this issue Jan 8, 2025 · 1 comment
Open

Daytona ignores no_proxy env variable #1692

bafzachris opened this issue Jan 8, 2025 · 1 comment
Labels
bug Something isn't working Needs Investigation This issue needs a team member to investigate its status. never stale An issue that never goes stale

Comments

@bafzachris
Copy link

bafzachris commented Jan 8, 2025

Describe the bug
I am trying to setup daytona in my local enterprise environment. We are using a http(s) proxy that only forwards default ports. I setup a local frps env. Daytona connects successfully to the frps instance when the proxy env variables are empty. However in this case daytona is unable to download any images. When I configure a proxy daytona cannot connect to frps as it is trying to connect to localhost via proxy.

I get the following error messages when no proxy is configured:

INFO[0000] Starting local container registry...
INFO[0000] Starting api server on port 3986
INFO[0000] Starting headscale server...
FATA[0010] proxy error: type [http] not supported when vhost http port is not set If you are using a VPN or firewall, please read our troubleshooting guide at https://daytona.io/docs/misc/troubleshooting#connectivity-issues

I get the following error messages when a proxy is configured and no_proxy is set to localhost:

daytona serve
INFO[0000] Starting local container registry...
INFO[0000] Starting headscale server...
INFO[0000] Starting api server on port 3986
FATA[0000] login to the server failed: DialTcpByHttpProxy error, StatusCode [403]. With loginFailExit enabled, no additional retries will be attempted

To Reproduce
Steps to reproduce the behavior:

  1. Setup local frps
  2. Setup no_proxy=localhost,127.0.0.1 http_proxy=<PROXY_URL> and https_proxy=<PROXY_URL>

Expected behavior
Daytona should ignore the proxy for localhost when the no_proxy env variable is set.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Linux
@bafzachris bafzachris added the bug Something isn't working label Jan 8, 2025
@Tpuljak
Copy link
Member

Tpuljak commented Jan 8, 2025

@bafzachris thanks for opening the issue. We'll definitely investigate this.

In the meantime, maybe setting your custom FRPS configuration in daytona might help.

You can open the daytona server configuration found at ~/.config/daytona/server/config.json and configure the custom FRPS endpoint there.

@Tpuljak Tpuljak added Needs Investigation This issue needs a team member to investigate its status. never stale An issue that never goes stale labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs Investigation This issue needs a team member to investigate its status. never stale An issue that never goes stale
Projects
None yet
Development

No branches or pull requests

2 participants