Unable to open Windy webpage. Gets error " Error: Forbidden.Your client does not have permission to get URL / from this server
-
YES, this is affecting many people with Starlink connections - myself and at least 4 friends, we are all Windy subscribers. The Windy support is clueless - I tried contacting them. Ground VPN works, normal Starlink IP's get blocked!
-
Many Starlink IP's got blocked from accessing the Windy server. Please fix this ASAP. Me and a few friends this started happening to are all Premium subscribers, and I am sure there is a vast number of Starlink users across the globe, and especially in Europe and around the Mediterranean area who are not able to access Windy since more than a week ago. Your support seems clueless about this issue and you already have one other thread about this.
-
@Ivo-Kalushev
How and where did you contact the Windy support ? -
In Atlantic North now: no problem with Starlink, with or without VPN, both browser and App OK. Regarding the IP above (better not publish your IP in public, BTW), it looks like the hosting server is in Sofia, Bulgaria and that it is building up a bad spam reputation :
https://cleantalk.org/blacklists/as14593/217.142.20.0/22
InOctober 2025, 180 spamming IP addresses in that networktoday 95 spam active IPs, spam rate 9%... Not everybody is using Windy only, unfortunately.
Cannot speak anything about Windy's hosting policies, and are they automatically blacklisting that network (and they will not tell you that in public), but I have doubts that they would whitelist your IP alone, since it can change.
I would advise using a VPN, or sailing away until Starlink changes the ground station. -
Hello, thanks for reporting, we're super sorry for the problems. Can you please let us know what specifically is happening? Is the web app not working, or our mobile app? Where are you currently located? Are you getting any specific error? A screenshot would be ideal.
If you are more technical and know what this means, could you use verbose
curlorwgetto fetch any problematic site and paste all headers you are getting in your response? -
Hello, thanks for reporting, we're super sorry for the problems. Can you please let us know what specifically is happening? Is the web app not working, or our mobile app? Where are you currently located? Are you getting any specific error? A screenshot would be ideal.
If you are more technical and know what this means, could you use verbose
curlorwgetto fetch any problematic site and paste all headers you are getting in your response? -
Hi all, we're sorry for the issues you're facing. As you can imagine, it's a bit difficult for us to test this, since we don't have a Starlink antenna located in the Mediterranean. If anyone here is more technically inclined and is facing the blocking, could you try running
curl -v https://windy.comin your terminal and paste the output here, together with your IP, location, etc?Just for the record, we are not blocking anyone intentionally, have no automated blockers enabled and actually make quite a lot of effort to be reachable even in countries like China, which implement blocking measures on their side.
-
Also, please, if you can tell me which specific country you are in, not just the "Mediterranean," it would be great. Furthermore, is the 403 Forbidden webpage branded in any way? Does it, e.g. have Google branding?
-
@idefix37 Through support@windy.com
-
@selverob said in Unable to open Windy webpage. Gets error " Error: Forbidden.Your client does not have permission to get URL / from this server:
curl -v https://windy.com
Here is the Terminal output for curl -v https://windy.com:
Last login: Thu Nov 27 09:13:05 on ttys000 iv@Iv-MacBook-Air ~ % curl -v https://windy.com * Host windy.com:443 was resolved. * IPv6: (none) * IPv4: 35.201.88.123 * Trying 35.201.88.123:443... * Connected to windy.com (35.201.88.123) port 443 * ALPN: curl offers h2,http/1.1 * (304) (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/cert.pem * CApath: none * (304) (IN), TLS handshake, Server hello (2): * (304) (IN), TLS handshake, Unknown (8): * (304) (IN), TLS handshake, Certificate (11): * (304) (IN), TLS handshake, CERT verify (15): * (304) (IN), TLS handshake, Finished (20): * (304) (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF * ALPN: server accepted h2 * Server certificate: * subject: CN=windy.com * start date: Nov 20 13:36:30 2025 GMT * expire date: Feb 18 14:32:25 2026 GMT * subjectAltName: host "windy.com" matched cert's "windy.com" * issuer: C=US; O=Google Trust Services; CN=WR3 * SSL certificate verify ok. * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://windy.com/ * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: windy.com] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.7.1] * [HTTP/2] [1] [accept: */*] > GET / HTTP/2 > Host: windy.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely sent off < HTTP/2 403 < content-type: text/html; charset=UTF-8 < referrer-policy: no-referrer < content-length: 295 < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 < 403 Forbidden <h1>Error: Forbidden</h1> <h2>Your client does not have permission to get URL <code>/</code> from this server.</h2> <h2></h2> * Connection #0 to host windy.com left intact iv@Iv-MacBook-Air ~ % -
Hi there, we have contacted Starlink and according to their employees, they have engaged in talks with Google and are working on resolving this blocking issue. It should be fixed within a few days.
Trust me, we are taking this seriously, I almost fell out of the window trying to set up Starlink in our office for testing, but, unfortunately, we are on a different ground station than you guys, so, to our dismay, Windy worked without any problems on it.
-
@selverob Thank you! :)))
