ANSWERED Remote access to Emby behind Airvpn

[adminnas 0]

Hi, I'm trying to set up a Docker with Gluetun and another one running Emby to do remote access to the Emby server. I managed to make it work to access my server remotely, however, the speed seems to be super slow. I'm having a 1000/1000Mb network, but the maximum up speed when it was playing was 1.5 MB/s. Is there some potential way to optimize? Or is it just my network's problem?
The following is my Docker Compose file. Has anyone tried to use AirVPN's port forwarding to access Emby remotely? Can anyone please help me check if there's something wrong with my setup?
 

services:

gluetun_emby:

image: qmcgaw/gluetun:latest

container_name: gluetun_emby

cap_add:

- NET_ADMIN

# devices:

# - /dev/net/tun:/dev/net/tun

environment:

- VPN_SERVICE_PROVIDER=airvpn

- VPN_TYPE=wireguard

- WIREGUARD_PRIVATE_KEY=xxx

- WIREGUARD_PRESHARED_KEY=xxx

- WIREGUARD_ADDRESSES=xxx

- SERVER_REGIONS=Europe

- FIREWALL_VPN_INPUT_PORTS=9268

- FIREWALL_OUTBOUND_SUBNETS=192.168.0.0/16

- TZ=Europe/Copenhagen

ports:

- 8096:8096

- 8920:8920

- 9268:9268

restart: unless-stopped

emby:

image: emby/embyserver

container_name: embyserver

network_mode: "service:gluetun_emby"

environment:

- UID=1000

- GID=10

- TZ=Europe/Copenhagen

volumes:

- ./programdata:/config

- /volume1/BitDownload/Link/Movies:/data/Movies

- /volume1/BitDownload/Link/TVSeries:/data/TVSeries

devices:

- /dev/dri:/dev/dri

restart: on-failure

Edited ... by adminnas

[Staff 10142]

Hello!

Please try various WireGuard's interface MTU, starting from 1280 bytes and slowly increasing it, and check whether you have a specific value which improves the upload speed. GlueTun's environment variable setting WireGuard interface MTU is WIREGUARD_MTU. You can set it in the compose file environment: section. Remember to re-start the container each time you change the setting. Example:

environment:
- UID=1000
- GID=10
- TZ=Europe/Copenhagen
- WIREGUARD_MTU=1280

Although you are probably in the EU, where such behavior would be illegal except when forced by congestion or exceptional causes, please note that some ISPs could cap UDP in upload even on symmetric lines (we mention UDP because WireGuard works over UDP). Please check the "traffic management" policy of your ISP, just in case.

Kind regards
 

[adminnas 0]

1 hour ago, Staff said:

Hello!

Please try various WireGuard's interface MTU, starting from 1280 bytes and slowly increasing it, and check whether you have a specific value which improves the upload speed. GlueTun's environment variable setting WireGuard interface MTU is WIREGUARD_MTU. You can set it in the compose file environment: section. Remember to re-start the container each time you change the setting. Example:

environment:
- UID=1000
- GID=10
- TZ=Europe/Copenhagen
- WIREGUARD_MTU=1280

Although you are probably in the EU, where such behavior would be illegal except when forced by congestion or exceptional causes, please note that some ISPs could cap UDP in upload even on symmetric lines (we mention UDP because WireGuard works over UDP). Please check the "traffic management" policy of your ISP, just in case.

Kind regards
 

Thank you for your response! I didn't find any related policy on my ISP's website, so I assume it's ok to change. 

I have another question, if I set the server to be Europe in config generation, will it automatically change the actual server for better performance during connection? Or is it only changing when I restart my Gluetun Docker?

[Staff 10142]

10 minutes ago, adminnas said:

if I set the server to be Europe in config generation, will it automatically change the actual server for better performance during connection? Or is it only changing when I restart my Gluetun Docker?

Hello!

GlueTun offers a remarkable integration with AirVPN and in general will not consider the configuration file to determine the end point. Instead, it will evaluate specific environment variables, please see here:
https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/airvpn.md#optional-environment-variables

Even if you set SERVER_REGIONS=Europe or something similar, a new end point will be determined only upon disconnection or container restart. Under no circumstance a connection will be intentionally and suddenly broken and then re-established to a different server without the operator's intervention.

Remember that the mentioned environment variables will be correctly evaluated when the VPN_SERVICE_PROVIDER variable is set to airvpn:
VPN_SERVICE_PROVIDER=airvpn

Kind regards