Networking on ottercoconut's Blog

Synology NAS Proxy and Emby Configuration

Mon, 16 Feb 2026 11:12:15 +0800

Recently, when using v2rayA on my Synology NAS, I encountered an issue where incorrect time synchronization caused it to stop working properly, which in turn prevented Emby from scraping metadata. Although I don’t know the exact reason, it’s an old problem. The version was very old, and I was using a Docker image from a third-party application store; currently, Docker can’t pull images via direct connection either. Here is my experience with solving this:

Reinstall v2rayA
Configure the Docker version of Emby.

Reference Websites:

Linux Backup Installation Method - v2rayA

XTLS/Xray-core: Xray, Penetrates Everything. Also the best v2ray-core. Where the magic happens. An open platform for various uses.

Implementing Transparent Proxy on Synology - v2rayA

sjtuross/syno-iptables: Some missing iptables modules for Synology

Setting up Proxy for Container Manager (Docker) on Synology DSM 7.2 - CSDN Blog

v2rayA

According to the official v2rayA documentation, there is no specially adapted version for Synology, so we use the generic binary file for installation. Since we cannot pull files from GitHub over a direct connection, we download it on our computer and transfer it to the NAS. In addition, the installation steps below are actually slightly different from the official documentation.

Copy v2rayA and xray

1
2
3
4


cp v2raya_linux_x64 /usr/local/bin/v2raya
cp xray /usr/local/bin/
chmod +x /usr/local/bin/v2raya
chmod +x /usr/local/bin/xray

Copy the GFWList proxy rule files included with xray: geoip.dat and geosite.dat
1 2 3

cd /usr/local/share mkdir xray cp .../g* xray

Modify the service configuration file

1

sudo vi /etc/systemd/system/v2raya.service

The content was generated by ChatGPT combined with the official documentation:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16


[Unit]
Description=v2rayA Service
After=network.target

[Service]
Type=simple
User=root
Environment="V2RAYA_CONFIG=/usr/local/etc/v2raya"
Environment="V2RAYA_LOG_FILE=/tmp/v2raya.log"
Environment="XRAY_LOCATION_ASSET=/usr/local/share/xray"
ExecStart=/usr/local/bin/v2raya --passcheckroot
Restart=on-failure
LimitNOFILE=1000000

[Install]
WantedBy=multi-user.target

Activate v2rayA. According to the official documentation, run it as a service
1 2

sudo systemctl start v2raya sudo systemctl status v2raya
Configure it to start up automatically on boot. Theoretically, the configuration is complete after this step. Along the way, I also solved the issue of transparency proxy not working on Synology.
1 2

sudo systemctl enable v2raya sudo systemctl is-enabled v2raya

Activate Transparent Proxy

arch	kernel	iptables version	system model	platform version
apollolake	4.4.180+	v1.8.3	DS918+	7.0.1-42218
apollolake	4.4.59+	v1.6.0	DS918+	6.2.3-25426
broadwell	3.10.105	v1.6.0	DS3617xs	6.2.3-25426
bromolow	3.10.105	v1.6.0	DS3615xs	6.2.3-25426
geminilake	4.4.180+	v1.8.3	DS920+	7.1-42661
geminilake	4.4.302+	v1.8.3	DS220+	7.2-64570

Due to the characteristics of the Synology system, first determine the architecture based on your model, then select the appropriate files for your machine from the downloaded modules from the GitHub repository (for example, my DS224 is geminilake).

Upload the corresponding ko modules to /lib/modules/, and upload the corresponding so modules to /usr/lib/iptables/, and that’s it.

Run sudo -i and then run the following insmod commands to attempt loading the ko kernel modules. Because the modules depend on each other, they must be loaded in a specific order.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21


insmod /lib/modules/nfnetlink.ko
insmod /lib/modules/ip_set.ko
insmod /lib/modules/ip_set_hash_ip.ko
insmod /lib/modules/xt_set.ko
insmod /lib/modules/ip_set_hash_net.ko
insmod /lib/modules/xt_mark.ko
insmod /lib/modules/xt_connmark.ko
insmod /lib/modules/xt_comment.ko
insmod /lib/modules/xt_TPROXY.ko
insmod /lib/modules/xt_socket.ko
insmod /lib/modules/iptable_mangle.ko
insmod /lib/modules/textsearch.ko
insmod /lib/modules/ts_bm.ko
insmod /lib/modules/xt_string.ko

insmod /lib/modules/nf_nat_ipv6.ko
insmod /lib/modules/nf_nat_masquerade_ipv6.ko
insmod /lib/modules/ip6t_MASQUERADE.ko
insmod /lib/modules/ip6table_nat.ko
insmod /lib/modules/ip6table_raw.ko
insmod /lib/modules/ip6table_mangle.ko

However, after a system reboot, the modules need to be reloaded, so generate a script with the above content at /usr/local/bin/load_v2raya_mods.sh.

Then restart the v2rayA service:

1

sudo systemctl restart v2raya

Emby

After configuring v2rayA, even though I used the method of modifying the configuration file, Emby’s traffic still couldn’t successfully pass through v2rayA. After various fruitless attempts to modify the IP configuration, it naturally occurred to me that this was caused by Docker running as a host service.

After modifying the configuration on v2rayA multiple times, I finally found that enabling the transparent proxy solved the problem, and it also fixed the issue of being unable to connect to the Docker repository. But a bigger problem arose: enabling the transparent proxy caused all external network access to fail (fortunately, local network connections still worked). I think “transparent proxy” can be understood as a “global proxy”.

For the issue of setting up a proxy specifically for Docker (Container Manager), please refer to the links in the preface.

Select Emby in “Images” and run it. Add the path to the media library in “Volume Settings”, add three environment variables in “Environment”, and select host mode in “Network”:
1 2 3

HTTP_PROXY = http://127.0.0.1:20171 HTTPS_PROXY = http://127.0.0.1:20171 NO_PROXY = localhost,127.0.0.1
Complete the basic setup, install the previous anime-related plugins, and the scraping was successful.

How to Use Host Proxy on WSL2

Fri, 30 Jan 2026 16:31:20 +0800

Since I’ve been frequently downloading various models with Python recently, I finally decided to solve the long-standing issue of WSL2 not being able to use the Windows host’s proxy. After wasting half an afternoon, I finally got it working. With the help of my capable assistant Gemini, the main steps are as follows:

.wslconfig settings in Windows
Core settings of v2rayN
Firewall settings in Windows
Cleaning up old settings in WSL2
~/.bashrc settings in WSL2
curl -v testing in WSL2

References:

Advanced settings configuration in WSL | Microsoft Learn

WSL2 使用 V2RayN 局域网 proxychains 代理方案 · Issue #2653 · 2dust/v2rayN

记一次用wsl2中共享宿主机的代理-v2rayN - 沉迷于学习，无法自拔^_^

.wslconfig

Access your personal account folder in Windows. Press Win + R, enter %UserProfile%, and hit Enter.
Check if there is a .wslconfig file. If not, create a new text file and name it .wslconfig.

Paste the following content into .wslconfig:

1
2
3
4
5
6
7


[wsl2]
# Enable mirrored networking mode
networkingMode=mirrored
# Allow WSL2 to access Windows localhost
localhostForwarding=true
# Automatically synchronize proxy settings (optional: true/false)
autoProxy=true

Note that the autoProxy parameter determines how WSL2 handles the proxy. Setting it to true means you don’t need to configure ~/.bashrc anymore, but the problems are:

When we use the env | grep -i proxy command, we will see many strange network-related variables, even though the proxy does successfully work.
The proxy cannot be toggled on or off within WSL2, causing a lot of traffic to go through the proxy unnecessarily.

Later, we will set it to false so that we can easily control the proxy switch inside WSL2, ensuring a clear and transparent WSL2 system.

In the Windows terminal, enter wsl --shutdown to shut down WSL2.

v2rayN

In the basic settings of v2rayN (version V7.15.7 at the time of writing), enable “Allow connections from the LAN” and “Open a new port for the LAN” (optional).
At the bottom left of the v2rayN client’s main interface, you can see the port open for the internet, which is 10810 in my case.
The system proxy here is “Set system proxy automatically”, and the routing mode is “Bypass (Whitelist)”.
Then select a node and keep v2rayN running.

FireWall

Type “firewall” in the Windows search box and select Windows Defender Firewall.
Click “Allow an app or feature through Windows Defender Firewall”.
Find or add v2rayN.exe and its core programs (such as v2ray.exe or xray.exe), ensuring that both Private and Public are checked. The usual paths are under v2rayN\ and v2rayN\bin\xray, respectively.
In the advanced settings of the firewall, create a new inbound rule to allow TCP traffic on port 10810 (corresponding to v2rayN).

wsl2

Cleaning Up Old Settings

1
2
3
4
5
6
7
8


# 1. Clear old, messy proxy environment variables
unset http_proxy
unset https_proxy
unset no_proxy

# 2. Re-set correct proxy (pointing to localhost port in mirrored mode)
export http_proxy="http://127.0.0.1:10810"
export https_proxy="http://127.0.0.1:10810"

Ensure that you have enabled mirrored networking mode in the first step and successfully restarted WSL2. Of course, this step is not strictly necessary either, because ~/.bashrc will automatically handle these old variables later.

~/.bashrc

1
2


# Same applies to other editors
sudo vim ~/.bashrc

After multiple experiments with Gemini, here is the content to append to the bottom of ~/.bashrc:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22


function proxy_on() {
 # Thoroughly clean up any residual variables (prevent conflicts from mixed case)
 unset http_proxy https_proxy ALL_PROXY NO_PROXY HTTP_PROXY HTTPS_PROXY all_proxy no_proxy
 
 # Set the port you verified works (since 10810 was tested successfully, use 10810)
 export hostip="127.0.0.1"
 export port="10810"
 
 export http_proxy="http://$hostip:$port"
 export https_proxy="http://$hostip:$port"
 export all_proxy="socks5://$hostip:$port"
 
 # no_proxy here only keeps localhost
 export no_proxy="localhost,127.0.0.1"
 
 echo "WSL Proxy: ON (127.0.0.1:10810)"
}

function proxy_off() {
 unset http_proxy https_proxy ALL_PROXY NO_PROXY HTTP_PROXY HTTPS_PROXY all_proxy no_proxy
 echo "WSL Proxy: OFF"
}

After saving the above content, enter:

1

source ~/.bashrc

And then:

1

curl -I https://www.google.com

The following output should appear, indicating a successful connection:

I also tested it with ping, which didn’t work but doesn’t affect its usability.

1

HTTP/1.1 200 Connection established

I tried downloading the model again, and it successfully worked:

1
2


import gensim.downloader as api
wv_from_bin = api.load("glove-wiki-gigaword-200")

Solution If It Still Fails

The most effective method is, after completing the above steps, to enter the following in WSL2:

1

curl -v https://www.google.com

Then feed the output result to an AI, and it will tell you what to do.