what should I do?

[AsleepMing]

Hi everyone,

What on earth is going on with GitHub Education verification? My long-used old account always fails the application, yet newly registered accounts can get all kinds of free perks without any hassle. I can’t connect at all without a VPN, but I’m not allowed to use one during the application. Submitting proof doesn’t help either. I keep getting this message every time:
Every time I apply for educational benefits, it prompts as shown in the picture: 'You must configure your browser and operating system to allow location access. You may not use a VPN. If you believe that our information about your school is incomplete or incorrect, then please select the' My selected school has incorrect or incomplete information, e.g. domains or campus location 'option when submitting a GitHub Education support ticket.' However, I am currently on campus . I have applied many times already, what should I do？
Why don't you go after accounts that use reverse proxies or resell benefits every single day, instead of constantly blocking legitimate users like me?

[AviJxn]

Hi, I understand how frustrating this can be — GitHub Education verification can sometimes fail due to strict location and eligibility checks.

Here are a few things you can try:

1. Disable VPN completely
   Make sure you are not connected to any VPN, proxy, or private DNS. Even background VPN apps can cause rejection.

2. Enable location services

• Turn on location access in your browser
• Allow location permission for GitHub
• Ensure your system location services are enabled

3. Use a stable campus network
   Try applying using your official campus Wi-Fi instead of mobile data. GitHub often checks IP consistency with your institution.

4. Verify your documents carefully
   Make sure your student ID or documents:

• Clearly show your name
• Match your GitHub account name
• Include a valid date

5. Submit a support ticket (important)
   If it still fails, choose:
   "My selected school has incorrect or incomplete information"

Then explain your situation clearly and attach proof.

6. Avoid multiple rapid attempts
   Repeated applications in a short time can trigger automatic rejections. Wait a few days before retrying.

---

If none of these work, it's likely a system-level verification issue, and only GitHub support can resolve it manually.