That’s interesting. My original problem actually disappeared after a few days on its own and didn’t come back so I just let it be. However, just a week or two ago, I created some new n8n instances in kubernetes, and one of them is exhibiting this same behavior! I was starting to wonder if it was the load balancer somehow, but that wouldn’t explain why it works fine for the other /rest endpoints and for the other instances.
I’ll be sure to update here if I find a solution.
Hey @Justin_C , that was it. It appears that after the license is activated, the node process needs to be restarted and until it is, the service behaves in an inconsistent manner.
I’m running a simple deployment, on the basic SQLite DB. Hopped in the container and cycled the node service, rather than the POD.
Once this issue occurs again, could you please try to open the “Usage & Plan” section in your instances’ settings panel? This will retrigger the license renewal and therefore should refresh the features set for your instance. An instance restart also triggers the license renewal.