Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warp issues #1531

Open
shenyiyouge opened this issue Dec 20, 2024 · 3 comments
Open

warp issues #1531

shenyiyouge opened this issue Dec 20, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@shenyiyouge
Copy link

Since I updated to Xray 24.12.18, my Warp stopped working. The original key became invalid, and replacing it with any new key also doesn't work. Please see the attached image,I’m not sure if others have this issue.
微信截图_20241220081240

@shenyiyouge shenyiyouge added the bug Something isn't working label Dec 20, 2024
@mostafaznv
Copy link

I’ve been experiencing this issue since yesterday.

@mostafaznv
Copy link

mostafaznv commented Dec 21, 2024

It may have something to do with IPv6.
When I enable Warp, pinging, for example, instagram.com switches to IPv6 and then freezes.
However, without warp, it uses ipv4 and works as expected.

(Just thoughts, it might be wrong)

Update:

2024/12/21 09:05:49 WARNING - X-UI: get udp connections failed:open /proc/net/udp6: no such file or directory
2024/12/21 09:05:49 WARNING - X-UI: get tcp connections failed:open /proc/net/tcp6: no such file or directory
2024/12/21 09:05:47 WARNING - X-UI: get udp connections failed:open /proc/net/udp6: no such file or directory
2024/12/21 09:05:47 WARNING - X-UI: get tcp connections failed:open /proc/net/tcp6: no such file or directory
2024/12/21 09:05:45 WARNING - X-UI: get udp connections failed:open /proc/net/udp6: no such file or directory

How can I force warp to use ipv4?

@mostafaznv
Copy link

mostafaznv commented Dec 21, 2024

I resolved my server issue with warp/wireguard and wanted to share my experience in case it helps someone.

For some reason, I had left ipv6 unassigned on my VPS from the start. It worked fine until last night.
After troubleshooting through the panel, checking xray logs, and so on, I realized the issue might be related to ipv6.
To fix it, I assigned an IPv6 to my VPS and configured it using Netplan:

sudo nano /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
    eth0:  # Replace 'eth0' with your network interface
      addresses:
        - 192.168.1.100/24  # Existing IPv4
        - 2001:db8::1/64    # Add your IPv6 here
      gateway4: 192.168.1.1
      gateway6: 2001:db8::1
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4
          - 2001:4860:4860::8888  # Google IPv6 DNS
          - 2001:4860:4860::8844
sudo netplan apply

And it worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants