Skip to content

Commit 4dadc4e

Browse files
authored
Update hosting.md
Fixed VPN section about firewall rules and updating DNS.
1 parent 896251f commit 4dadc4e

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

hosting.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ The next step is to enable HTTPS. Unlike domain and VPN, an HTTPS certificate ca
8383

8484
I decided to test if I can access Hideout over HTTPS, and if I'll be redirected when I attempt HTTP connection. I found the website timing out. After checking every corner, it turned out that on my firewall, I've only setup port-forwarding for port 80, but not port 443. After I forwarded port 443, the HTTPS connection and redirection worked immediately.
8585

86-
At this point, I've successfully hosted a working instance of Hideout on my laptop. But if I'm to send a Hideout link to others, I'd expose the public IP of my home to both the recipients, and the unprivate platform where I send the link. So I need to host Hideout behind a VPN. Fortunately, port-forwarding is supported by Mullvad VPN: https://mullvad.net. I installed its open-source app on my laptop, and followed Mullvad's port-forwarding guide: https://mullvad.net/en/help/port-forwarding-and-mullvad/. It was a rather simple process. I didn't need to touch my router or firewall. I also disabled the port-forwarding on my firewall for port 80 and 443, because the port-forwarding doesn't happen on the firewall anymore. It's handled by Mullvad. A caveat is that Mullvad assigns me a random port number. Let's assume it's 50000 in this guide. This requires me to change the `listen 443 ssl` in `hideout-demo.com.conf` to `listen 50000 ssl`. Below is the final config. Notice the commented block at the end too.
86+
At this point, I've successfully hosted a working instance of Hideout on my laptop. But if I'm to send a Hideout link to others, I'd expose the public IP of my home to both the recipients, and the unprivate platform where I send the link. So I need to host Hideout behind a VPN. Fortunately, port-forwarding is supported by Mullvad VPN: https://mullvad.net. I installed its open-source app on my laptop, and followed Mullvad's port-forwarding guide: https://mullvad.net/en/help/port-forwarding-and-mullvad/. Overall, it was a rather simple process. A caveat is that Mullvad assigns me a random port number. Let's assume it's 50000 in this guide. Before it would work, I disabled the port-forwarding on my firewall for port 80 and 443, and instead enabled port-forwarding for port 50000. Then I updated the DNS of the domain to point to the "Out" IP of Mullvad, which can be seen by clicking the expand arrow on the app's home interface. The new port also required me to change the `listen 443 ssl` in `hideout-demo.com.conf` to `listen 50000 ssl`. Below is the final config. Notice the commented block at the end too.
8787
```
8888
server {
8989
@@ -128,6 +128,4 @@ server {
128128
#
129129
#}
130130
```
131-
I modified it further after Certbot's operation. See the commented out block at the end. Make sure that the port number being listened on is 50000, with this line `listen 50000 ssl;`.
132-
133-
At this point, I've successfully hosted Hideout on a computer I physically own, behind VPN, over HTTPS. I can access it in browser at `https://www.hideout-demo.com:50000`. Note that no piece of the URL can be left out. I need to specify all of `https`, `www`, and port number `50000`.
131+
At this point, I've successfully hosted Hideout on a computer I physically own, over HTTPS, behind a VPN. I can access it in browser at `https://www.hideout-demo.com:50000`. Note that no piece of the URL can be left out. I need to specify all of `https`, `www`, and port number `50000`.

0 commit comments

Comments
 (0)