<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Service (incl premium) is not available through a VPN]]></title><description><![CDATA[<p dir="auto">The service and the community are not available through my VPN. The problem is definitely it, as switching VPN location or disconnecting, corrects the service.</p>
<p dir="auto">Two issues:</p>
<ol>
<li>
<p dir="auto">First and less important. The error you generate does not say anything about the VPN being blocked<br />
Here it is:<br />
<img src="/assets/uploads/files/1721305391918-screenshot-2024-07-18-at-15.19.28.png" alt="Screenshot 2024-07-18 at 15.19.28.png" class=" img-fluid img-markdown" /></p>
</li>
<li>
<p dir="auto">Second and more important .<br />
You CANNOT decide to shutdown a service to PAYING customers just because of their network settings. VPNs are widely used and as I’m on a public networks for weeks they are my only option.<br />
The bug is that your login server shuts down my connection.<br />
<img src="/assets/uploads/files/1721305870199-screenshot-2024-07-18-at-15.26.16-resized.png" alt="Screenshot 2024-07-18 at 15.26.16.png" class=" img-fluid img-markdown" /><br />
And - since you require a pass through the login EVERY time (there is a separate bug about that by another frustrated customer) - you shut down the whole weather service.</p>
</li>
</ol>
<p dir="auto">Now - I understand prevention from DDoS attacks somewhat and filtering VPNs is the crudest and one of the more ineffective ways to do it.<br />
But you should allow a path for your paying customers to access the service. The login server should not be part of that “protection” and allow login. And then once logged as a premium account all such “protections” should be bypassed.</p>
<p dir="auto">(Excuse any potential typos, as I’m writing from a phone. You don’t allow my laptop in)</p>
]]></description><link>https://community.windy.com/topic/34436/service-incl-premium-is-not-available-through-a-vpn</link><generator>RSS for Node</generator><lastBuildDate>Wed, 10 Jun 2026 07:13:41 GMT</lastBuildDate><atom:link href="https://community.windy.com/topic/34436.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 18 Jul 2024 12:31:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Service (incl premium) is not available through a VPN on Sat, 20 Jul 2024 20:10:28 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/suty" aria-label="Profile: Suty">@<bdi>Suty</bdi></a><br />
If you need it to troubleshoot, I can provide ip address, protocol and a browser log.</p>
]]></description><link>https://community.windy.com/post/195043</link><guid isPermaLink="true">https://community.windy.com/post/195043</guid><dc:creator><![CDATA[enterfornone]]></dc:creator><pubDate>Sat, 20 Jul 2024 20:10:28 GMT</pubDate></item><item><title><![CDATA[Reply to Service (incl premium) is not available through a VPN on Thu, 18 Jul 2024 13:45:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/enterfornone" aria-label="Profile: enterfornone">@<bdi>enterfornone</bdi></a> We will check this case and let you know, however, if we are not able to replicate the issue, we won't be able to fix that. However, I will go through that.</p>
]]></description><link>https://community.windy.com/post/194855</link><guid isPermaLink="true">https://community.windy.com/post/194855</guid><dc:creator><![CDATA[Suty]]></dc:creator><pubDate>Thu, 18 Jul 2024 13:45:32 GMT</pubDate></item><item><title><![CDATA[Reply to Service (incl premium) is not available through a VPN on Thu, 18 Jul 2024 12:52:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/suty" aria-label="Profile: Suty">@<bdi>Suty</bdi></a><br />
In this case is a VPN Unlimited service with a WireGuard protocol through Austria. Same server works via OpenVPN.<br />
Yet WireGuard works via an US VPN, so it’s a trial and error.<br />
Sometimes I get through  on a second, sometimes on a third-fourth try.</p>
<p dir="auto">My point with this bug report is general. You should a) not restrict the login server and b) not have any restrictions on logged in (especially premium) members</p>
<p dir="auto">It’s a replicable bug, but I don’t want to “fix” this or that ip and just for my preferred service. A general fix for logged customers is needed.</p>
]]></description><link>https://community.windy.com/post/194850</link><guid isPermaLink="true">https://community.windy.com/post/194850</guid><dc:creator><![CDATA[enterfornone]]></dc:creator><pubDate>Thu, 18 Jul 2024 12:52:23 GMT</pubDate></item><item><title><![CDATA[Reply to Service (incl premium) is not available through a VPN on Thu, 18 Jul 2024 12:34:31 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/enterfornone" aria-label="Profile: enterfornone">@<bdi>enterfornone</bdi></a> Could you please share more info about used VPN tool? We normally use VPN and I tested the access via VPN as well many times and there shouldn't be any issue with it.</p>
]]></description><link>https://community.windy.com/post/194840</link><guid isPermaLink="true">https://community.windy.com/post/194840</guid><dc:creator><![CDATA[Suty]]></dc:creator><pubDate>Thu, 18 Jul 2024 12:34:31 GMT</pubDate></item></channel></rss>