FAQ

Open Instances, click Deploy an instance, give it a name, then click Deploy. The details are in Deploying an instance.

About four minutes. You do not have to watch the screen: Continue in the background closes the progress window, and an email tells you when the instance is ready.

Either your plan has reached its number of instances, and the Maximum number of instances reached window offers Upgrade; or your usage already exceeds your plan's limits, and you first need to free some space. See the quotas.

No. The name makes up the address of your portal, https://your-name.lizpack.com, and cannot change after deployment. Choose it carefully: lowercase letters, digits and hyphens.

No. A name stays reserved after its instance is deleted. To recover an old name, write to support.

Yes, by opening Versions (optional) when you deploy. There you pick QGIS Server and Lizmap Web Client among versions that work together. If you choose nothing, the instance gets the versions marked Recommended.

The Update button on the instance page becomes active when a newer version exists. Your projects, files and database are not touched, and the instance goes back to its previous versions if the update fails. It is included in the Pro and Enterprise plans. See Updating an instance.

The instance then shows the Failed or Error badge. Write to support: we can often repair it without losing anything. If you delete it, its name stays reserved; a new deployment will need another one.

It is online at https://your-name.lizpack.com. On the instance page, the Map portal card gives this address and, under Administrator access, the link to the Lizmap administration with its credentials.

In the three-dot menu of its card, on the Instances page, choose Delete, enter your account password, then click Delete permanently. Projects, files and database are erased for good. See Start, stop, delete.

Bank card, monthly or yearly, renewed automatically. Mobile Money, for the yearly subscription only and without automatic renewal. And the licence key. See payment methods.

Emails warn you 7 days, 3 days, 2 days and the day before the due date. On expiry, your instances stop, database included, and switch to Subscription expired. Their projects, files and databases are kept for 60 days; before any deletion, three more emails warn you. Renew from Subscriptions to get everything back.

If your files or databases exceed the limit, the web services of your instances stop, but the database and Files stay open so you can free space. If you have too many instances, only the most recent ones over the limit stop, completely. Everything restarts on its own once you are back under the limits. See the quotas.

Look at its badge on the Instances page. Quota exceeded: free some space or change plan. Subscription expired: renew your subscription. Suspended: the stop comes from our team, write to support. In all three cases, your data is intact.

Yes. As soon as the payment is confirmed, your instances restart within the limits of the new plan, and an email confirms it.

Yes, at any time, from Plans LizPack. You pay the full price of the new plan. The time left on the old one is converted according to the ratio of the two prices: towards a more expensive plan, it gives you fewer days than you had left. Time left on a free trial is not carried over.

No: on plans below yours, the button reads Downgrade not possible. Likewise, a yearly subscription cannot go back to monthly.

On Plans LizPack, click I have a licence key under the plan you want. Enter the key, click Check the key, check the plan shown, then Confirm the activation. See licence keys.

The free plan lasts the number of days shown on its card, and its limits are shown there too. It can be activated only once per account: after that, its card shows Trial already used. You receive an email on activation, two days before the end, the day before, then on expiry with the paid plans.

Yes. The Yearly switch on the plans page shows the saving compared with monthly (ten months paid for twelve), and each card then shows its yearly price.

In Subscriptions, Invoices card. Each invoice downloads as a PDF. See invoices.

Yes. It is issued on activation, sent by email and filed with the others in Invoices.

On the instance page, unfold the PostgreSQL / PostGIS card: Connection details gives the database, user, password, host and port to enter in QGIS. These settings are reserved for the Pro plan and above. See the database.

The Lizmap administration one, as the QGIS Server card on the instance page says: login and password are under Administrator access. The LizPack Publisher extension, on the other hand, signs in with your LizPack account email and password.

Yes. Each instance has its own database, its own file space and its own QGIS Server. See data security.

Always keep your own copy: your QGIS projects on your computer, and a regular export of your databases. The client area does not offer restoration; if you lose data, write to support. An instance stopped for expiry or overrun keeps its data for 60 days.

QGIS 3.16 or later. See installing the plugin.

Open your project in QGIS, then LizPack Publisher. In the Sign in tab, enter your account email and password and click Sign in. In the Projects tab, choose the destination folder on your instance, then click Publier vers Lizmap. See publishing a project.

Almost all of them: QGIS projects, styles, vector and raster layers, GeoPackage, images, documents, spreadsheets, archives. Refused are scripts and code (.py, .js, .php, .sh…), executables (.exe, .msi…), configuration files (.env, .ini, .conf) and .sql files. See the formats.

Its badge on the Instances page tells whether it is Running. On its page, each service is Active, Inactive or Degraded. A service that is Inactive or Degraded while the instance is started should be reported to us.

The Projects, Storage and Database counters are measured about every five minutes while you are using the client area, and also after each deployment or file upload.

Not for an instance: its address is always a subdomain of lizpack.com. If you need one, write to support.

Yes. Each instance's QGIS Server serves these four OGC standards for published projects. The service address is on the QGIS Server card of the instance page. See QGIS Server.

The Pro or Enterprise plan. The My team page shows the number of members and your plan's ceiling; pending invitations count towards it. See the team.

No. They work on your account, with your instances and your quotas. They only need a LizPack account opened with the address you invited. Only the account owner, however, can order a dedicated database.

Yes. The selector in the header, My account, switches from one account to another under Switch account; My personal instances brings you back to your own account. It lists three teams at most. See switching account.

They immediately lose access to your instances and data. Their own account and their own instances are not affected.

Yes, with Invite and the same address. You set their role and permissions again. A declined invitation is sent again with Invite again.

7 days. An expired invitation still shows as Pending and blocks a new invitation to the same address: remove it, then invite again.

Only those who have the View billing permission. Among the ready-made roles, only Administrator has it. See the roles.

The instance database is part of the instance: it stops, is suspended and disappears with it. A dedicated database is subscribed separately, from Databases: it has its own storage and stays in service whatever happens to your instances. See dedicated databases.

Unfold Connection details on the database card, create a PostGIS connection in QGIS with these settings, add your layers to the project, then publish it. The instance's QGIS Server then reads the layers straight from the database. See connecting to a dedicated database.

Yes, PostGIS is installed from deployment, along with postgis_topology, hstore, uuid-ossp and pg_trgm.

Yes. Each database has its own subscription, its own invoice and its own storage size.

An email warns you at 60, 75, 80, 90 and 95%. At 100%, the database switches to Running · grace period: you have 24 hours to get back under the limit. After that, or as soon as usage exceeds 110%, the database is stopped. It does not restart by itself: write to support, who will restart it so you can delete data. See the database quota.

It is stopped, then kept for 60 days before being deleted for good. Renew its subscription within that time to get it back.