Skip to content

Conversation

@kedare
Copy link

@kedare kedare commented Aug 12, 2025

Update install.sh to configure all internal network as dual stack.

This allow to have true end to end IPv6 connectivity whenever possible, this allows for example IPv6 clients to reach IPv6 backend without losing the original source IPv6 in the process.

Fixes Dokploy/dokploy#2349 (comment)

There may have others changes to reflect if any part of the code also creates IPv6 (in clusters mode for example, I don´t have any cluster to test this part), but basically the only change that would be needing to these calls would be to create the new networks as dual stack (equivalent of --ipv6 --ipv4 of the cli command)

@kedare kedare requested a review from Siumauricio as a code owner August 12, 2025 19:11
@kedare kedare changed the title Add compatibility with end-to-end IPv6 install.sh: Add compatibility with end-to-end IPv6 Aug 12, 2025
@agentHits
Copy link

Image

Installing Server Dependencies: ✅
SSH connection error: connect ENETUNREACH 2a03:6f00:a::c9e0:22 - Local (:::0) client-socket
Error: SSH connection error: connect ENETUNREACH 2a03:6f00:a::c9e0:22 - Local (:::0) ❌

I am completely unable to connect dokploy via ipv6 directly, although from console I connect locally (using proxy with ipv6 connection support) as my ISP doesn't support ipv6 connection by default, but via terminal client + socks5 proxy I can easily access my vps via ipv6.

Please fix Dokploy to work over ipv6 connection

check #2509 (Dokploy/dokploy#2509)

@kedare
Copy link
Author

kedare commented Sep 6, 2025

I don´t think this part is related to this PR, it looks like you cannot connect over SSH which has nothing to do with this PR and have to be taken care on the server OS directly.
I have no issue on my Dokploy setup to connect over SSH or to the Dokploy web interface over IPv6, are you sure you don´t have any firewall blocking IPv6 or something like this ?

@kedom1337
Copy link

kedom1337 commented Dec 2, 2025

Did you actually test if this works? I tried these changes and IPv6 traffic did not work properly. After doing some research it seems that docker swarm itself still has no proper IPv6 support.

@kedare
Copy link
Author

kedare commented Dec 4, 2025

Yes I am using it on my dokploy infra and it's working fine.

(On my case it's a single node dokploy setup, I think for multi-nodes setup there are also some nodejs code to update to run docker API calls with the proper parameters for dual stack)

You can try by yourself:

curl https://echo.dokploy.keda.re/
{
  "path": "/",
  "headers": {
    "host": "echo.dokploy.keda.re",
    "user-agent": "curl/8.14.1",
    "accept": "*/*",
    "x-forwarded-for": "2001:67c:da8:1002:9c44:20ee:d06b:6c08",
    "x-forwarded-host": "echo.dokploy.keda.re",
    "x-forwarded-port": "443",
    "x-forwarded-proto": "https",
    "x-forwarded-server": "e3ed92fdd4bc",
    "x-real-ip": "2001:67c:da8:1002:9c44:20ee:d06b:6c08",
    "accept-encoding": "gzip"
  },
  "method": "GET",
  "body": "",
  "fresh": false,
  "hostname": "echo.dokploy.keda.re",
  "ip": "2001:67c:da8:1002:9c44:20ee:d06b:6c08",
  "ips": [
    "2001:67c:da8:1002:9c44:20ee:d06b:6c08"
  ],
  "protocol": "https",
  "query": {},
  "subdomains": [
    "dokploy",
    "echo"
  ],
  "xhr": false,
  "os": {
    "hostname": "8362405f60ee"
  },
  "connection": {}
}

@kedom1337
Copy link

Yeah I have a multi-node setup that's probably it, gotta look into that. Thanks

@kedare
Copy link
Author

kedare commented Dec 15, 2025

I remember when taking a look there were some part of the NodeJS that would do the equivalent of what I did with the install script but I did not modify them yet as I don't have any multi-nodes setup to test it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

X-Real-IP and X-Forwarded-For are wrong with IPv6 clients

3 participants