DIG Network
Is HTTPS:443 not implemented yet? #18
-
|
In the install instructions it mentions ports 80, 4159, 4160, 4161... but in open_ports.sh/ask_open_ports it's also including port 443/HTTPS... but the .dig/remote/.nginx/conf.d/default.conf file never gets configured to enable 443? I think that means if you choose to enable the nginx reverse-proxy... it will offer to open 443 in your firewall... but never use it? That's OK if it's not ready yet: I'm just making sure I shouldn't have any responses on port 443. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
If you set up the reverse proxy and specify a hostname, the installer will provide an option to set up Let's Encrypt for that hostname. Were you asking about a different setup or something else? |
Beta Was this translation helpful? Give feedback.
-
|
I only saw the setup ask about managing firewall/forwarding ports that mentioned 443... just didn't see it in the list of ports in the install guide. I'm not using a hostname and HTTPS isn't something I need for the alpha. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
There will be a time where i do a second pass on the installer to try to make it more understandable. Thank you for bearing with it so far. |
Beta Was this translation helpful? Give feedback.
If you set up the reverse proxy and specify a hostname, the installer will provide an option to set up Let's Encrypt for that hostname. Were you asking about a different setup or something else?