When connecting to n8n the workflow screen immediately dies with a 404 message and when capturing requests the n8n.example.com/rest/put?sessionId=something request returns a 404 message with
Cannot GET /rest/push
However if I change the header value of the request from
I get a 200 response. I have Nginx in front of n8n but I can’t spot anything in the setup that would cause this. The request is obviously making its way to n8n for it to return that response in the 404.
Anyone run into anything like this before?