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

Build completely broken in codespaces now. #13

Open
cforsythe opened this issue Dec 27, 2023 · 0 comments
Open

Build completely broken in codespaces now. #13

cforsythe opened this issue Dec 27, 2023 · 0 comments

Comments

@cforsythe
Copy link

Hello,

I have a codespace build of nextjs, and vite from the codespaces templates
and neither of them work out of the box due to https issues. I'm not sure if the hosting domain for the port forwarded sites has changed, but using .dev means the browser is forced to connect using https and I am pretty sure that neither nextjs or vite are configured to use https which causes ssl issues.

If I load the codespace into my local vs code instance and start the vite/nextjs instance there I can connect just fine. So I imagine for these templates to work again either:

  1. Don't serve these port forwarded instances from a .dev domain so developers can connect to them via http
  2. Update these templates to work for a https connection and make that a default since .dev domains can only be connected to via https

Simple Browser

ssl_issue

Normal Browser (see SSL error)

ssl_issue_2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant