Dockers don't have internet access while being connected to WireGuard VPN

[ERKO901]

Current Behavior

I have set up WireGuard server on OVH VPS because of its antiddos and when I connect to it from my ubuntu server everything except the dockers work, such as ssh or https. I can normally connect to panel and manage servers but when I try to start them and there is some task that needs internet connection it throws error.
Here is my WireGuard Configuration on ubuntu server where the panel is hosted

Address = 10.1.1.2/24
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
MTU = 1420

[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxx
Endpoint = xxxxxxxxxxxxxxxxxxxxxx:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25

and here is the OVH VPS config

Address = 10.1.1.1/24
ListenPort = 51820
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AllowedIPs = 10.1.1.2/32```

### Expected Behavior

I expect the docker to successfully connect to internet.

### Steps to Reproduce

Connect to WireGuard tunnel.

### Panel Version

1.11.10

### Wings Version

1.11.13

### Games and/or Eggs Affected

_No response_

### Docker Image

_No response_

### Error Logs

```bash

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[ItsRaelx]

Hi @ERKO901, I had the same issue when i was experimenting with Wireguard and docker. Solution is pretty simple, lower your MTU value in wings config:

(/etc/pterodactyl/config.yml)

  network:
    interface: 172.18.0.1
    dns:
    - 10.45.0.254
    name: pterodactyl_nw
    ispn: false
    driver: bridge
    network_mode: pterodactyl_nw
    is_internal: false
    enable_icc: true
    network_mtu: 1500 (replace with 1420 or lower)

afterward remove your pterodactyl network using: docker network rm [network_name]
and restart wings (should recreate missing network with correct MTU)

[ERKO901]

Hello @ItsRaelx Thanks for helping. I have changed config from this

  network:
    interface: 172.18.0.1
    dns:
    - 1.1.1.1
    - 1.0.0.1
    name: pterodactyl_nw
    ispn: false
    driver: ""
    network_mode: pterodactyl_nw
    is_internal: false
    enable_icc: true
    network_mtu: 1500```
into this 
``` docker:
  network:
    interface: 172.18.0.1
    dns:
    - 10.1.1.2  // Here I am not sure what to put here
    name: pterodactyl_nw
    ispn: false
    driver: ""  // Here I typed bridge but after restarting it is back as ""
    network_mode: pterodactyl_nw
    is_internal: false
    enable_icc: true
    network_mtu: 1420```

And when I try allocation with private ip 192.168.7.198 it does the same and does not work, neither WireGuard ip 10.1.1.2 or 0.0.0.0

[ItsRaelx]

You shouldn't need to change anything besides mtu and deleting the network in docker, not sure why it switches the driver for you.

[ERKO901]

@ItsRaelx , I am still trying to fix it but the dockers still have no internet access. Do you have any other idea how to fix it

[ItsRaelx]

@ItsRaelx , I am still trying to fix it but the dockers still have no internet access. Do you have any other idea how to fix it

Did you recreate docker networks as I told?

[ERKO901]

Yes I did but it still doesn't work.

[danny6167]

Converted to discussion as this is not a bug with the software and the issue tracker is not for support.