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
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
Normal Browser (see SSL error)