NITRO_SSL_CERT/KEY path value leading to "no start line" errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
I'm using Nitropack v2.12.4 and I've had to augment the built code in order for my SSL certs to work
I had been getting "no start line" errors for 2 days or so. I knew my cert and key were valid, but for some reason, no matter what I changed, nitro refused to serve my project via https mode.
So finally I decided to change the nitro source code in order to try and see where the issue was.
I placed the paths in my .env file like so:
NITRO_SSL_CERT="/path/to/certs/cert.pem"
NITRO_SSL_KEY="/path/to/certs/key.pem"
Nitro got the ssl paths but still I got the same error.
I had to change:
to this:
And this ended up working.
Now my question is, is this a bug?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing HTTPS startup with NITRO_SSL_CERT and NITRO_SSL_KEY set to quoted paths, then inspect the SSL configuration path handling described in the issue. Done means valid certificate and key paths from the environment work without changing Nitro's built source and no "no start line" error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100