Waystones Cloud · Guides
Troubleshooting
Fixes for common problems with uploads, deployments, private services and plan limits in Waystones Cloud.
Uploading data
"Only GeoPackage (.gpkg) files are supported"
Waystones Cloud takes GeoPackages. Convert other formats first — in QGIS with Export → Save Features As… → GeoPackage, or with GDAL:
ogr2ogr -f GPKG data.gpkg input.shp
The QGIS plugin does the conversion for you, for any vector layer QGIS can open.
"This GeoPackage has no feature tables"
The file only contains raster tiles or attribute tables without geometry. Raster data isn't supported yet. Check the file in QGIS: each layer you want to publish should show up as a vector layer.
The coordinate system is wrong
If the file doesn't declare a coordinate system, Waystones assumes WGS 84 (EPSG:4326). Set the correct CRS in QGIS (Layer Properties → Source → Assigned Coordinate Reference System), save the layer to a new GeoPackage and upload that.
"This upload would exceed your … GB storage quota"
The upload would take you over your plan's storage (2 GB on the free plan). Delete projects or files you no longer need, buy the Extra Storage add-on, or upgrade on the billing page.
Deploying
"Cannot deploy — your model expects layers that were not found in the dataset"
The data model lists layers that aren't in the uploaded file or database — usually because the file was replaced with one whose tables have different names. Replace the dataset with one that has the expected tables, or create a new project from the new file.
"This service is already being deployed"
A deployment for the same service is still in progress. Wait for it to finish — its log is on the project page — and try again.
"Your subscription payment has failed"
Deploys are paused while a payment is overdue. Update your payment method on the billing page.
The first request is slow
Services run on demand and sleep when idle. The first request after a quiet spell wakes the service and takes a moment longer; the following ones are fast.
Using a service
HTTP 401 "Private deployment requires a valid API Key"
The project is private. Send a key with every request — Authorization: ApiKey <your-key> as a header, or ?api_key=<your-key> on the URL. In QGIS, the URL parameter is the simplest: add it to the connection URL. See Private services.
HTTP 429 "QUOTA_EXCEEDED"
On the free plan, a service pauses once it has served 250,000 requests in a month and starts again at the beginning of the next month. Upgrade for higher limits and no pause — see Pricing.
Changes to the title or license don't show up
Service details are applied when a service is deployed. After saving, open the project's Deploy page and deploy again to the same slug.
QGIS only shows 10 features at a time
That's the API's default page size. QGIS normally pages through all features automatically; if you query the API yourself, add limit (up to 1000) and follow the next link.
Still stuck?
Email [email protected] with your project's slug and what you tried. For bugs in the open-source tools, open an issue for the QGIS plugin or the designer. On a paid plan, the AI assistant in the dashboard can also help.