github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #2132] Not support IPV6. #1696

New issue

Closed

opened 2026-05-05 13:05:12 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 13:05:12 -06:00

Owner

Originally created by @sheng-di on GitHub (Dec 5, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2132

The config file:

[gpustaker]
type = http
local_port = 8000
local_ip = [2001:da8:204:1043:f393:7869:xxxx:c9]
custom_domains = example.com

However, when connected to my domain, the following error occurs:

2020/12/05 10:13:27 [E] [proxy.go:793] [4c5a274fae2a860a] [gpustaker] connect to local service [2001:da8:204:1043:f393:7869:1dd3:c9:8000] error: dial tcp: address 2001:da8:204:1043:f393:7869:xxxx:c9:8000: too many colons in address

Originally created by @sheng-di on GitHub (Dec 5, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2132 The config file: ``` [gpustaker] type = http local_port = 8000 local_ip = [2001:da8:204:1043:f393:7869:xxxx:c9] custom_domains = example.com ``` However, when connected to my domain, the following error occurs: ``` 2020/12/05 10:13:27 [E] [proxy.go:793] [4c5a274fae2a860a] [gpustaker] connect to local service [2001:da8:204:1043:f393:7869:1dd3:c9:8000] error: dial tcp: address 2001:da8:204:1043:f393:7869:xxxx:c9:8000: too many colons in address ```

gitea-mirror

2026-05-05 13:05:12 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:05:16 -06:00

Author

Owner

@Becods commented on GitHub (Dec 5, 2020):

If the FRPC is deployed locally, do not add local_ip.

If you have an IPv4 intranet address, use IPv4.

FRP may not support IPv6 completely.

@Becods commented on GitHub (Dec 5, 2020): If the FRPC is deployed locally, do not add `local_ip`. If you have an IPv4 intranet address, use IPv4. FRP may not support IPv6 completely.

gitea-mirror commented

2026-05-05 13:05:16 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 6, 2020):

@BecodReyes There is no difference between IPv4 and IPv6, golang net package support them default.

@378978764 Your IP address is not correct format detect by golang net package. Make sure your have [ ] in both side of local_ip. It's not seen in log.

@fatedier commented on GitHub (Dec 6, 2020): @BecodReyes There is no difference between IPv4 and IPv6, golang net package support them default. @378978764 Your IP address is not correct format detect by golang net package. Make sure your have `[` `]` in both side of `local_ip`. It's not seen in log.

gitea-mirror commented

2026-05-05 13:05:18 -06:00

Author

Owner

@sheng-di commented on GitHub (Dec 9, 2020):

@BecodReyes There is no difference between IPv4 and IPv6, golang net package support them default.

@378978764 Your IP address is not correct format detect by golang net package. Make sure your have [ ] in both side of local_ip. It's not seen in log.

The IP address is indeed enclosed in square brackets, both in the configuration file and log. This ip address is copied from the ipconfig command.

@sheng-di commented on GitHub (Dec 9, 2020): > @BecodReyes There is no difference between IPv4 and IPv6, golang net package support them default. > > @378978764 Your IP address is not correct format detect by golang net package. Make sure your have `[` `]` in both side of `local_ip`. It's not seen in log. The IP address is indeed enclosed in square brackets, both in the configuration file and log. This ip address is copied from the `ipconfig` command.

gitea-mirror commented

2026-05-05 13:05:19 -06:00

Author

Owner

@sheng-di commented on GitHub (Dec 9, 2020):

If the FRPC is deployed locally, do not add local_ip.

If you have an IPv4 intranet address, use IPv4.

FRP may not support IPv6 completely.

Unfortunately, the service is deployed in a local area network, and this machine can only be accessed through an IPv6 address.

@sheng-di commented on GitHub (Dec 9, 2020): > If the FRPC is deployed locally, do not add `local_ip`. > > If you have an IPv4 intranet address, use IPv4. > > FRP may not support IPv6 completely. Unfortunately, the service is deployed in a local area network, and this machine can only be accessed through an IPv6 address.

gitea-mirror commented

2026-05-05 13:05:20 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 9, 2020):

2020/12/05 10:13:27 [E] [proxy.go:793] [4c5a274fae2a860a] [gpustaker] connect to local service [2001:da8:204:1043:f393:7869:1dd3:c9:8000] error: dial tcp: address 2001:da8:204:1043:f393:7869:xxxx:c9:8000: too many colons in address

@378978764 From the log your pasted, there are no brackets. 2001:da8:204:1043:f393:7869:xxxx:c9:8000 is not correct address, it should be [2001:da8:204:1043:f393:7869:xxxx:c9]:8000.

I test the correct adrress and it's all right.

@fatedier commented on GitHub (Dec 9, 2020): `2020/12/05 10:13:27 [E] [proxy.go:793] [4c5a274fae2a860a] [gpustaker] connect to local service [2001:da8:204:1043:f393:7869:1dd3:c9:8000] error: dial tcp: address 2001:da8:204:1043:f393:7869:xxxx:c9:8000: too many colons in address` @378978764 From the log your pasted, there are no brackets. `2001:da8:204:1043:f393:7869:xxxx:c9:8000` is not correct address, it should be `[2001:da8:204:1043:f393:7869:xxxx:c9]:8000`. I test the correct adrress and it's all right.

gitea-mirror commented

2026-05-05 13:05:21 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 24, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 24, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

Rows
Columns