Configure Firefox Containers to Access the Diode Network
There are many ways to access various resources published to the Diode Network. The method covered in this article uses the official Firefox Container add-on to create a specific container within Firefox that can serve Diode Network content via the socks proxy provided by the Diode CLI.
Part 1: Configure Firefox
- Install the Official Firefox Multi-Account Container Add-On
- Open the Container Add-On by clicking it's icon (shown below) in the top left of Firefox

- At the bottom of the Container Add-On pop-up, click "Manage Containers"
- Click "New Container" at the top, give it a Name, Color, and Icon, then click "OK".
- Install the Container Proxy Firefox Add-On
- Open the Container Proxy Add-On by clicking it's icon (shown below) in the top left of Firefox
- In the left menu, select the "Proxies" option. Then click the plus button to add a proxy.

- Fill out the proxy details as shown below. If you already have a Diode Network socks proxy server available, you can replace "localhost" with the ip address of that server. Otherwise, keep it as "localhost" and follow part 2 of this tutorial to configure the local socks proxy with the Diode CLI. Note that the username and password fields are intentionally left blank. When finished, click save.

- In the left menu, click the "Assign" option.
- Find the container that you created in Step 4 and change it's drop down menu from "Directly" to "Diode Network"
Part 2: Configure your local Diode Network proxy
- Install the Diode CLI
- Open a terminal window and run the command
diode socksd
You will need to have this command running whenever you want to access Diode Network content in your Firefox container.
Part 3: Test the Connection
- In Firefox, right click on the new tab icon to open the container selection menu. From this menu, select the container you created in Step 4 of Part 1. A new tab will open inside the container you selected.
- Inside the new container tab, navigate to
http://betahaus-berlin.diode
. Note: make sure to usehttp
and NOThttps
.
Even without https, your connection is still secure via the Diode Network
- If the tab loads the Diode video player, then your connection is configured properly! You can see an example of what it should look like via the Web2 gateway run by Diode.