GitHub Community
New API + VPN problem #136017
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm running Scala Steward locally to keep a few of my private repos up to date. As of a few weeks ago, all was fine, but then automated PRs stopped appearing and the SS logs showed errors like the following:
It doesn't seem to be an auth issue (Scala Steward is creating branches on the repos and pushing commits successfully) - I can see that those have happened when browsing the repos via the web UI) - it looks like just PR creation is failing now (used to work fine).
When I dropped my VPN connection (Mullvad) and ran SS from bash using the same script that launches it from cron, it worked! No error. Which leads me to wonder if the GH API is VPN-hostile? It doesn't seem like a firewall-y problem (not just an IP block) because it seems clear the GH API server is receiving the request, it's just rejecting it for some reason. Are VPNs blocked at the app level, or might Mullvad (or other VPN services) be rewriting the POST request in some way that GH is unhappy with? If so, what sort of rewriting might that be that could cause the 400 error?
Beta Was this translation helpful? Give feedback.
All reactions