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

After using the daytona create command, http changed to https. #1329

Open
TS35 opened this issue Nov 9, 2024 · 4 comments
Open

After using the daytona create command, http changed to https. #1329

TS35 opened this issue Nov 9, 2024 · 4 comments
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

@TS35
Copy link

TS35 commented Nov 9, 2024

Hello, I set up Gitea locally and tried to create a workspace using Daytona, with the providers URL set to http://localhost:3000/. However, after executing the "daytona create" command, an error appears as shown in the image. It seems that the requested URL is changing from http to https, which is causing the access to fail. How can I resolve this issue?

test1

@TS35 TS35 added the bug Something isn't working label Nov 9, 2024
@idagelic
Copy link
Member

idagelic commented Nov 9, 2024

Hi, thanks for submitting the issue. We pushed a fix regarding this in v0.41.0 but it's possible we missed something - can you please let me know the output of daytona -v to be sure?

@TS35
Copy link
Author

TS35 commented Nov 9, 2024

Hi, thanks for submitting the issue. We pushed a fix regarding this in v0.41.0 but it's possible we missed something - can you please let me know the output of daytona -v to be sure?

OK. As shown in the figure below, the execution result shows that I'm using version v0.42.
test2

@idagelic
Copy link
Member

idagelic commented Nov 9, 2024

Got it. It's possible we missed something during testing - we will release a fix on Tuesday and I will get back to you to confirm.

@Tpuljak Tpuljak added never stale An issue that never goes stale Needs Investigation This issue needs a team member to investigate its status. labels Nov 11, 2024
@idagelic
Copy link
Member

@TS35 We just did some testing and realized the issue lies in the need for the Git provider to be accessible to the container (Daytona workspace) cloning the repo.

That means you should expose the Gitea port 3000 using e.g. https://theboroer.github.io/localtunnel-www/, change the domain in the Gitea config to the new endpoint, rerun it and then daytona gp update to change the Base API URL to the newly generated URL to get this to work.

The http -> https fix will be released to the providers so this issue can be closed when that is done. Let me know if you have any questions

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

3 participants