You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug is about the VPN setup script, and not WireGuard VPN itself
Describe the issue
A clear and concise description of what the bug is.
After the auto successful installation amazon ec2 ubuntu server . I connected to it on android and also tried to connect to it on laptop, but to no avail. no internet connection
To Reproduce
Steps to reproduce the behavior:
...
...
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Add error logs to help explain the problem, if applicable.
Server (please complete the following information)
OS: [e.g. Debian 11]
Hosting provider (if applicable): [e.g. GCP, AWS]
Client (please complete the following information)
Device: [e.g. iPhone 12]
OS: [e.g. iOS 15]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
@azharrasheed Hello! Please make sure that you have opened UDP port 51820 in your Amazon EC2 server's security group. The script in this repo has been tested and worked fine in those tests.
WireGuard VPNs can be blocked by firewalls such as the GFW in mainland China. For those use cases please look into alternative solutions such as Shadowsocks.
Checklist
Describe the issue
A clear and concise description of what the bug is.
After the auto successful installation amazon ec2 ubuntu server . I connected to it on android and also tried to connect to it on laptop, but to no avail. no internet connection
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Add error logs to help explain the problem, if applicable.
Server (please complete the following information)
Client (please complete the following information)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: