This is a fork of a original https-portal, with additional features intended to use in DAppNode as one of the core packages. All of its existing features should remain functional.
API was added through which containers proxied through portal can be dinamically chosen. By default server listens at port 5000 for GET methods add and remove both of which have to and from querry parameters i.e.
GET /add?from=<chosen-subodomain>&to=<internal-resource>
GET /remove?from=<chosen-subodomain>&to=<internal-resource>
Where chosen-subdomain is chosen external endpoint for forwarding and internal-resource is either IP or domain that resolves on the internal network.
When using DAppNode dyndns service, https-portal uses DAppNode certificate service to get wildcard certificates for the DAppNode dyndns domains which are provided for free. In this mode, following environment variables have to be set:
| Name | Value | Description |
|---|---|---|
| CERTAPI_URL | TBD | URL of remote signing service |
This mode can only be used within DAppNode as a package.
It is even possible to run DAppNode on your own domain. Your domain and all of its subdomains should resolve to the pubilc IP of the DAppNode. But please note, for every subdomain certificate is requested since it uses HTTP chalenges which cannot be used for issuing wildcard certificates. In this mode, following environment variables have to be set:
| Name | Value | Description |
|---|---|---|
| PUBLIC_DOMAIN | Your domain |