No workspace here (404)

Describe the problem/error/question

I am trying to use a webhook node to receive data from a web form using fetch. I have set up a reverse proxy with (valid ssl cert and open 443 port) to deal with the cors issue. Before even attempting posting from the web page I curl the webhook url directly and it works as expected, if I curl the proxy I get a 404 error.

The corresponding entry in the nginx access log is 2023-10-04 11:50:59 - - [04/Oct/2023:11:50:59 +0000] “POST /webhook-test/b3cef632-70a1-4ebf-a808-458a92a13e2e 2.0” 404 5662 “-” “curl/7.88.1”

curl -i -X POST https://[name of proxy]/webhook-test/b3cef632-70a1-4ebf-a808-458a92a13e2e

HTTP/2 404

server: nginx

date: Wed, 04 Oct 2023 11:38:10 GMT

content-type: text/html

vary: Accept-Encoding

access-control-allow-origin: *

access-control-allow-methods: GET, POST, OPTIONS

access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range

access-control-expose-headers: Content-Length,Content-Range

What is the error message (if any)?

No workspace here (404)

Your workspace was taken offline. This usually happens when a trial or subscription has ended.

Please share your workflow

“meta”: {
“instanceId”: “fb50c293f108e25b349984937ea511d4b44c3b8c7a86f96ae89e9ec47e87396b”
“nodes”: [
“parameters”: {
“authentication”: “headerAuth”,
“path”: “b3cef632-70a1-4ebf-a808-458a92a13e2e”,
“options”: {}
“id”: “a9f0039c-dbce-4ce8-954c-9c9c61402696”,
“name”: “Webhook”,
“type”: “n8n-nodes-base.webhook”,
“typeVersion”: 1,
“position”: [
“webhookId”: “b3cef632-70a1-4ebf-a808-458a92a13e2e”,
“credentials”: {
“httpHeaderAuth”: {
“id”: “Df6aB8IRInXVEAe7”,
“name”: “Header Auth account”
“connections”: {}

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.8.1
  • Database (default: SQLite): Default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud
  • Operating system: N/A

Any guidance would be appreciated

Hi @marketing_utc, welcome to the community, though I am very sorry you’re having trouble.

Custom domains aren’t supported by n8n cloud, so there currently is no “official” way to make this work. So I’d very much suggest self-hosting n8n here, as any workarounds implemented outside of actual n8n cloud functionality might stop working without warning.

That said, I suspect you’re simply not setting the Host header to match your n8n cloud instance’s hostname here.

If I configure a local caddy webserver to act as my reverse proxy like so…

localhost {

…I am getting the 404 response you have described as the load balancers for n8n cloud won’t process traffic for localhost (or the domain you are using):

However, once I configure my reverse proxy like so…

localhost {
    reverse_proxy {
        header_up Host

…I am getting the expected 200 response:

n8n also processes the request as expected:

These example configurations are of course Caddyfiles, but on the nginx site of things I believe proxy_set_header Host should do the job.

Hope this gives you a pointer as to what might be missing here :slight_smile:

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.