I have the subscriptions plugin up and running smoothly so far on a self-hosted discourse which I’m about to launch, however I just happened across the Billing tab and figured I should check what that looks like. I’d signed up myself but using a 100% off coupon so I think I should have something to see there.
When I go to the billing tab, I get an error message, then when I click try again, I’m seeing a warning that there was an error loading route due to the whos online plugin.
sorry to hear your troubles, but I suspect we might have fixed it last week, but its not yet deployed to your instance. Can you try to disable your ad-block if you have any and see if it works please?
I’m still having a hard time replicating this locally, so could you show me what you have in your browser console when loading that page? Maybe it will have something useful in it.
The network tab for “subscriptions” should look something like this:
I’m also curious if the admin subscription page loads? You can visit this url /admin/plugins/discourse-subscriptions/products and then click on the subscriptions tab.
Not sure if this is related, but we had the same problem a few days ago. I haven’t had time to analyze the problem, but my best guess is that it happens when we run out of memory.
A little context: According to the basic set up, it is used on Vultr’s HF server (4gb ram) and YJIT is also turned on. This works perfectly in general situations. The Who’s online plugin is also installed and AI checks posts, etc… But the subscription plugin is not installed. However, a few days ago, when we experienced this error, there was an increased use because we organized a fundraise for one of our member and there was much more interaction than usual. Which presumably overloaded the server. The user routes were not loaded and we experienced the above error. It also showed us that the problem is with the who’s online plugin. At that point, I turned off the AI automatic post check because that also didn’t work well on that situation and presumably that helped to get things working again.
I checked the CPU usage and it wasn’t high enough to cause this. So I think lack of memory may have caused this problem for us.