Technical & Advanced

Run WinWeatherBot on a VPS 24/7 — Setup Guide

4 replies Started May 2026
← Back to community
JK
OP May 2026

I've been running WIN Weather Bot on a Windows VPS for 3 weeks now and it's been rock solid. Going to write up exactly how I set it up since I see this question a lot. This is for the Pro plan server mode.

What you need: A Windows VPS (I use a €10/month Contabo plan), your WIN Weather Bot Pro license, and about 30 minutes.

TS
TECH May 2026

Great writeup incoming from jake_k. Let me add the official technical guidance from our side:

VPS requirements for running WIN Weather Bot server mode:

  • OS: Windows Server 2019/2022 or Windows 10/11 (64-bit)
  • RAM: minimum 2GB, 4GB recommended
  • CPU: 1 vCPU is sufficient
  • Location: Must be in a Polymarket-accessible jurisdiction (EU, UK, most of Asia, Latin America — NOT USA)
  • Port: 8765 must be accessible locally (no firewall changes needed for local-only mode)

Installation steps on a fresh Windows VPS:

  1. Download the WIN Weather Bot installer from your account dashboard
  2. Run the installer — it will place the files in the installation folder
  3. Double-click the WIN Weather Bot executable — the setup wizard will launch
  4. Enter your Polymarket credentials (API key, secret, passphrase, private key)
  5. Enter your WIN Weather Bot license key when prompted
  6. Once the main UI opens, configure your settings under ⚙ SETTINGS
  7. Click START — the server will launch automatically

To keep it running 24/7 after RDP disconnect:

The bot needs to stay running when you close your RDP session. The cleanest way is to use Windows Task Scheduler to launch it at startup:

schtasks /create /tn "WIN Weather Bot" /tr "C:\WIN Weather Bot\WIN Weather Bot.exe" /sc onstart /ru SYSTEM /f

Or alternatively, use a tool like NSSM to run it as a Windows service. This is the most reliable method for long-term VPS deployment.

Important: Your VPS must be located in a supported jurisdiction for the platform. If a VPS shows a persistent GEOBLOCK warning, its location isn't supported — choose a VPS in a supported region instead. The geo-check is a compliance safeguard, not a setting to bypass.

JK
May 2026

Adding to the above — one thing I ran into: after setting up the task scheduler, the bot launches fine but if your VPS restarts (maintenance, etc.) and no one is logged in via RDP, the bot launches in a hidden session. The UI won't be visible when you log back in but the server is still running in the background.

To check if it's running, open a command prompt and type:

curl http://localhost:8765/status

If you get a JSON response, the server is running. If not, restart it manually.

SP
May 2026

Which VPS providers work well? I tried Vultr USA and immediately got GEOBLOCK. Switched to Vultr Frankfurt and it works perfectly. Any other recommendations?

TS
TECH May 2026

Confirmed working locations from community reports:

  • 🇩🇪 Germany (Contabo, Hetzner, Vultr Frankfurt) — most popular, lowest latency to Polymarket EU infra
  • 🇳🇱 Netherlands (DigitalOcean Amsterdam, OVH Strasbourg)
  • 🇸🇬 Singapore (Vultr, DigitalOcean) — best for Asian market timing
  • 🇬🇧 UK (AWS London, Linode)
  • 🇧🇷 Brazil (Vultr São Paulo) — useful for South American weather markets

Do NOT use US-based VPS. Polymarket is not available in the United States and US IPs are blocked at the API level.