massalabs / massalabs/node-manager-plugin
use https for node url
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As described in this issue #41 https doesn't work on station.massa:33035. This create errors when using the node inside station and exploring website served in https as calling a http content from a https site is a [mixed content](https://developer.mozilla.org/fr/docs/Web/Security/Mixed_content?utm_source=mozilla&utm_medium=firefox-console-errors&utm_campaign=default) security issue.
In issue #41 we have implemented a quick fix: instead of using http://station.massa:33035, we use http://localhost:33035 which doesn't rise mixed content error.
But it would be good to be able to use https on nodes deployed via node manager plugin and use station.massa:33035 url for that.
We need to investigate why the certificate doesn't work. It may be related to commit 57ee468 in [station](https://github.com/massalabs/station) that aimed at fixing ssl certificate renewal.
Contributor guide
No contributing guide indexed for this repository
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 reviewing issue #41 and commit 57ee468 in the station repository, then investigate why HTTPS fails for station.massa:33035 while localhost avoids the mixed-content error. Done means the node-manager deployment serves HTTPS at the station.massa URL with a working certificate and no mixed-content errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100