Accept Bitcoin payments. Free, open-source & self-hosted, Bitcoin payment processor.
With this release, we are providing a migration path for legacy MySql and SQLite installations.
If you are a BTCPay Server integrators such as developer of Raspiblitz, Umbrel, Embassy OS or anybody running BTCPay Server on SQLite or MySql, please refer to the documentation.
While SQLite and MySQL should still be working for one year or two, we will not fix bugs related to those backend. (unless it impacts migration)
Some users experienced Error 500 after login on to BTCPay Server from the 1.7.6. If it is your case, to update on docker deployments via the UI, you need to:
https://{yourserver}/server/maintenance
There are two vulnerabilities fixed in this release. Those are not severe, as it requires the victim to actively click on a malicious link and public registration, but we recommend to update.
We also introduce a breaking change in the Greenfield API route /api/v1/stores/{storeId}/rates/configuration/preview
. (#4607)
This breaking change shouldn't impact the majority of people.
Integrators such as Raspiblitz or Umbrel: As part of our effort to make BTCPay Server more welcoming to plugins, we have made a change that may impact you.
Previously, when a user uninstalled or installed a new plugin, BTCPay Server would prompt them to restart the server by clicking on a button. Prior to version 1.7.4, this restart button was not functional due to being coupled to our own Docker deployment stack.
As of now, the restart button will instead terminate the BTCPay Server process. The process manager, such as systemd or docker should then automatically restart BTCPay Server. Please ensure that automatic restart capability exists.
We recommend you to update your plugins after this update.
DescriptionHashOnly
to Lightning invoice creation endpoint (#4411) @NicolasDorierDescriptionHash
in the Lightning invoice creation endpoint has been removed (#4411) @NicolasDorierinvoicewithdescriptionhash
anymoreallow-deprecated-apis=false