You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn’t a showstopper, as you can manually download the package and place it in the Roaming\BTCPayServer\Plugins\ folder. However, the different behavior complicates testing and debugging. I'm documenting this for future exploration and better understanding of why this happens.
The text was updated successfully, but these errors were encountered:
When the Download method is invoked, we return a 302 redirect to the URL of the *.btcpay package:
btcpayserver-plugin-builder/PluginBuilder/Controllers/ApiController.cs
Line 126 in 67f502e
When running btcpayserver-plugin-builder locally and hitting this method from another local BTCPay Server instance (in debug mode), the result is an HTTP 302 response to:
http://127.0.0.1:32827/satoshi/artifacts/admin-pass-reset/3/*.btcpay
On the other hand, using the default instance (https://plugin-builder.btcpayserver.org) returns an HTTP 200 with the content of the *.btcpay package.
This isn’t a showstopper, as you can manually download the package and place it in the
Roaming\BTCPayServer\Plugins\
folder. However, the different behavior complicates testing and debugging. I'm documenting this for future exploration and better understanding of why this happens.The text was updated successfully, but these errors were encountered: