github / github/codespaces-nextjs

Build completely broken in codespaces now.

Open
#13 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
152
Forks
210
PR merge metrics
No merged PRs in 30d

Description

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](https://github.com/github/codespaces-nextjs/assets/14841355/893d71b9-5697-41b2-ad79-457dc84ee6df)
### Normal Browser (see SSL error)
![ssl_issue_2](https://github.com/github/codespaces-nextjs/assets/14841355/9a4786aa-8e61-4370-9929-7f22d7463ff9)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Codespaces Next.js and Vite templates and inspect how their port-forwarded URLs handle HTTPS. Done means both templates launch from Codespaces and their forwarded sites load without SSL errors, either over HTTP or with working HTTPS configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, vite
Domain
developer-experience, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.