SSL

[shawnzhou1120]

Description

how to set the SSL for homepage?

Other

No response

[hejunchen]

I want to ask the same question.

[BassT23]

+1

[benphelps]

This is not a task homepage should need to handle, if you want to access it behind an SSL, setup a reverse proxy.

[BassT23]

done ;)

[modem7]

I thought the open source application means: feature driven by the user community, yes or no? If more users are asking for the SSL support feature, would it become the TASK of homepage?

Not at all. Homepage is a dashboard, not a reverse proxy or SSL termination application.

There are plenty of containers that will handle this (NGINX, Caddy, Traefik etc), so it makes no sense dedicating dev time for a function that has nothing to do with the project, and can (and should) be dealt with by something that is dedicated towards that end.

[jagadam97]

and basically the projects that provide SSL in built are projects catering to business use cases. or hold and share critical security data. I dont thing homepage falls under any of these

[AntonTerehov]

Hi @benphelps, I hope you're doing well!
Reverse proxy is a valid option, but why don't you want to add an option to provide a custom SSL certificate for a dashboard?
It may be an optional parameter in the docker-compose similar to that:
- /server/path/to/private.key:/etc/ssl/certs/homepage.key:ro
- /server/path/to/certificate.crt:/etc/ssl/certs/homepage.crt:ro \
The homepage can use these two certificates for the internal 443 port requests. If the user specifies custom_port:443 in the docker-compose and these two certificates, it'd become HTTPS.
I think it may be a relatively easy change that will allow the use of custom CAs widely used in home labs.
Thank you!

[AF360]

This is not a task homepage should need to handle, if you want to access it behind an SSL, setup a reverse proxy.

Not at all, it IS a task Homepage should handle!
Your application is unencrypted and even in a local environment I don't want to setup additional software like a reverse proxy just to heal this issue and having the traffic encrypted like it should be in the first place...
Also I don't get why you are so reluctant to offer this as Next.js now has (experimental) SSL-support.

[sochartgit]

This is relative to the webserver used by homepage, which puts focus onto next.js.
My understanding is SSL support for Next.js is still experimental.

[sochartgit]

That's a solution:
https://www.briangetsbinary.com/nextjs/software%20engineering/2023/04/26/nextjs-configuring-localhost-ssl.html

[sochartgit]

It works well without reverse proxy overhead

[ecwio]

When is this coming ? there is sensitive data in homepage. SSL is a must. At least provide a tutorial on how to setup a reverse proxy please ... You can't have unencrypted connection in 2024; even for a "local" site....

[AF360]

Apparently Ben has no intention to add SSL! :-(
And I don't want to setup a reverse proxy for a local site.

[laweschan]

setup reversed proxy should be another idea for protection, but honest I still prefer homepage has native support on ssl first.

you can edit /app/server.js and /app/package.json to enable it yourself

I'm using podman and self-signed cert for testing, take your own risk

for /app/server.js:
modify as:
const https = require('https')
const fs = require('fs')
const sslOptions = { key: fs.readFileSync('/app/config/homepage.key'), cert: fs.readFileSync('/app/config/homepage.crt') }
const server = https.createServer(sslOptions, async (req, res) => {....

for /app/package.json:
modify as:
"start": "node server.js", // previously "next start"

restart container, now your homepage should able to access https://

good luck

Lawes

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.