adam/ipfs-blog
1
0
Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-08-12 03:42:47 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update from Forestry.io

Browse Source 
Jessica Schilling updated src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md
This commit is contained in:
Jessica Schilling
2021-06-10 20:53:23 +00:00
committed by Forestry.io
parent be5aa0621d
commit 774f15e465
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md
+1 -1
View File
@@ -265,7 +265,7 @@ Ensure you specify DNS6 or DNS4, depending on if you're forming an IPv6 or IPv4
## 🔒 SSL (Nginx)
So far we've setup WebRTC-Star and p2p-circuit without SSL (unless you used the WebRTC-Star docker setup). If you want to use your nodes over the Internet, with a browser, they need to support SSL. If you're using the defaults currently WebRTC-Star should be running on port 9090 (no-SSL) and p2p-circuit will be on port 4011 (no-SSL). We're going to put those on port 9091 (SSL) and port 4430 (SSL), respectively.
So far we've setup WebRTC-Star and `p2p-circuit` without SSL (unless you used the WebRTC-Star docker setup). If you want to use your nodes over the Internet, with a browser, they need to support SSL. If you're using the defaults currently WebRTC-Star should be running on port 9090 (no-SSL) and p2p-circuit will be on port 4011 (no-SSL). We're going to put those on port 9091 (SSL) and port 4430 (SSL), respectively.
First ensure Nginx is installed, then obtain and install [Certbot](https://certbot.eff.org/docs/install.html).