Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem upgrading to 2.0.5 #966

Open
vsatmydynipnet opened this issue Jan 1, 2025 · 2 comments
Open

Problem upgrading to 2.0.5 #966

vsatmydynipnet opened this issue Jan 1, 2025 · 2 comments

Comments

@vsatmydynipnet
Copy link

A happy new year to all of you.

Since a longer time I run a server latest updated in November. Git log shows this as status:

commit f989152921e55b7b8275baac0d0fddd73701f951 (HEAD -> master, origin/master, origin/HEAD)
Author: Seth For Privacy <[email protected]>
Date:   Thu Nov 7 08:13:16 2024 +0100

    Bump Monero to v0.18.3.4 (#948)

System is based on Debian bullseye, upgraded to bookworm to see if this helps too.

When updating now it updates to version 2.0.5 of BTCPayServer and then I run into the problem, that 2 of the 7 shops ends up displaying a empty page after login.

Shops not having a point of sale and crowdfunding setup works after the update. (not tried Woocommerce integration till now).

Shops having a POS and Crowdfunding setup ends up in a empty page after login.

I checked all documentation and also read https://blog.btcpayserver.org/btcpay-server-2-0/ twice, but I do not see any error from my side. I run btc-update.sh as always.

Is there anything I have overseen?

Thank you for any hint. I was going back to a snapshot before running btc-update.sh, so currently everything works.

@dennisreimann
Copy link
Member

Can you check the logs and see if there's an error for those page requests that do not work? docker logs generated_btcpayserver_1

@vsatmydynipnet
Copy link
Author

I updated again and this is probably the error causing the problem in these 2 shops. I changed the xpubID to make it invalid:

fail: Microsoft.AspNetCore.Server.Kestrel: Connection id "0HN9BT1LT2MDD", Request id "0HN9BT1LT2MDD:00000001": An unhandled exception was thrown by the application.
System.InvalidOperationException: The exception handler configured on ExceptionHandlerOptions produced a 404 status response. This InvalidOperationException containing the original exception was thrown since this is often due to a misconfigured ExceptionHandlingPath. If the exception handler is expected to return 404 status responses then set AllowStatusCode404Response to true.
 ---> Newtonsoft.Json.JsonSerializationException: Error converting value "xpub661MyMwAqR-SOMELONGID-vCzQGKJzpFc6B-[legacy]" to type 'BTCPayServer.DerivationSchemeSettings'. Path 'BTC-CHAIN', line 1, position 136.
 ---> System.ArgumentException: Could not cast or convert from System.String to BTCPayServer.DerivationSchemeSettings.
   at Newtonsoft.Json.Utilities.ConvertUtils.EnsureTypeAssignable(Object value, Type initialType, Type targetType)
   at Newtonsoft.Json.Utilities.ConvertUtils.ConvertOrCast(Object initialValue, CultureInfo culture, Type targetType)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType)
   --- End of inner exception stack trace ---

I moved back to the snapshot, but i can retest pretty easy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@dennisreimann @vsatmydynipnet and others