Hi! I tried to setup a wireguard tunnel but it seems that something is wrong with QUIC confiuration. Here is my Docker compose: services: storj1: image: "storjlabs/storagenode:${IMAGE_TAG}" container_name: storj1 restart: unless-stopped stop_grace_period: 300s user: "${UID}…

Thanks. So, I decided to use OCI (Oracle Cloud) and it works! Thank you so much all for your help! It was really interesting and I learned so much! ps: I don’t which post I should tag as the solution. So I’ll tag this last one.

TLDR: your QUIC issue may not be related to routing. But it’s not worth debugging, ignore. This approach works and preserves source IPs for log analissys later: Hosting services behind a restrictive firewall/CGNAT using DNAT on a VPS... This is a short description of how to host servic…

Increase the read and write buffers to 7500000. See QUIC docs and Storj node FAQ about QUIC.

So I followed your tutorial and adapted the wireguard server config file to my setup (replacing 10.0.60.2 by 10.10.0.2 ; and ens3 by eth0). It seemed to work for a few minutes but then, I started to see some ERRORS in the logs, like that: 2026-01-08T19:45:20Z ERROR contact:service ping satellite …

[image] smokemodel: wireguard client to wireguard server (or the other way around), it doesn’t work. That’s the problem — the tunnel does not work. It does not make sense to triage further until tunnel works. How come it works first and then stops? Or you mean logss log failure after some ti…

With my initial configuration (in my original post), wireguard tunnel works. My client wireguard config: [Interface] PrivateKey = <wireguard client private key> Address = 10.10.0.2/24 Table = off [Peer] PublicKey = <Wireguard server public key> AllowedIPs = 10.10.0.0/0 Endpoint = 46.224.42.102:5…

This is your problem. (Wire guard client config). Something you missed in the tutorial. [image] smokemodel: [Peer] PublicKey = <Wireguard server public key> AllowedIPs = 10.10.0.0/0

I just changed it for: [Interface] PrivateKey = <Wireguard client private key> Address = 10.10.0.2/24 Table = off # Important : wg-quick ne touche pas à la table de routage principale [Peer] PublicKey = <Wireguard server public key> AllowedIPs = 10.10.0.1/32 Endpoint = 46.224.42.102:51820 Persi…

Question: Why are you forwarding port 51820 (wireguard) to 28967 (storj)? Answer: Because that’s the easiest way to break wireguard which uses UDP port 51820.

[image] smokemodel: I’m not really sure why we need to redirect incoming traffic on 51820 to Storj server (10.10.0.2) Holy crap. My bad. I command/replaced wrong value in my opus. I’ll fix it asap. Sorry about that! It was meant to be my non-standard storj port, not wireguard port, obviously…

Wireguard + VPS: need help for QUIC

Node Operators troubleshooting

arrogantrabbit January 7, 2026, 9:56pm 2

TLDR: your QUIC issue may not be related to routing. But it’s not worth debugging, ignore.

This approach works and preserves source IPs for log analissys later:

This may help workaround QUIC binding:

Ultimately, the guidance is to ignore: