I had a workflow that was working, but now I get an error that localhost is refusing to connect. I think it is n8n that is refusing the connection. Why would this start happening when my workflow was executing before?
Hey @bryanham1 hope all is well.
You should assume we don’t know what you are running and how you are running it when you ask the question. We also don’t have access to your computer/server. So how are you running it? Docker? npm?
where do you get it? how does it look? can you show it?
well again, are you sure it is still running? have you checked? can you show?
Ok, great start, go on…
I am running a call to the workflow using two approaches, one is the app I am creating in Visual Studio on my laptop, so that is using my local host, but is it the n8n host that is refusing? The second approach is my server, I publish my app from Visual Studio to my server and run the call there and get the same error message.
Now, I am making the webhook call from a url link in a webform, and it was working before on both my platforms, but now it does not?
Well there are generally two ways to have n8n running - in docker or via npm. Which one you are using?
I was running a version of n8n on my computer using --tunnel but it was too unstable so I am on a trial on the cloud version, BTW much more stable.
Ok, so you are using the cloud version of n8n.
When you are sending requests to localhost what are you targeting to reach?
I don’t understad, I had 5 workflows I was working on and they are gone now??? Only one workflow left? This is a big loss for me. I have to recreate them? what happened to them, I just looked to give you a copy and they are gone.
{
“nodes”: [
{
“parameters”: {
“path”: “8b316e5e-0a1d-4af4-9a49-4d54127ceefd”,
“responseMode”: “responseNode”,
“options”: {}
},
“type”: “n8n-nodes-base.webhook”,
“typeVersion”: 2,
“position”: [
16,
-16
],
“id”: “9c481f36-2173-46d6-b944-7f8d582a801b”,
“name”: “Webhook”,
“webhookId”: “8b316e5e-0a1d-4af4-9a49-4d54127ceefd”
}
],
“connections”: {
“Webhook”: {
“main”: [
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “e3c1647536678efae553663d350ffe92e3a297c7ca1b2b35540cea551000bc72”
}
}
{
“nodes”: [
{
“parameters”: {
“path”: “App_Data/Convert.zip”
},
“type”: “n8n-nodes-base.ftp”,
“typeVersion”: 1,
“position”: [
224,
-16
],
“id”: “82ff2afa-4995-4429-b4b3-de55643f3ce0”,
“name”: “FTP”,
“credentials”: {
“ftp”: {
“id”: “O57wAjOatW9n1UIx”,
“name”: “FTP account”
}
}
}
],
“connections”: {
“FTP”: {
“main”: [
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “e3c1647536678efae553663d350ffe92e3a297c7ca1b2b35540cea551000bc72”
}
}
{
“nodes”: [
{
“parameters”: {
“respondWith”: “binary”,
“responseDataSource”: “set”,
“inputFieldName”: “=data”,
“options”: {
“responseHeaders”: {
“entries”: [
{
“name”: “Content-Disposition”,
“value”: “attachment; filename="Convert.zip"”
}
]
}
}
},
“type”: “n8n-nodes-base.respondToWebhook”,
“typeVersion”: 1.4,
“position”: [
432,
-16
],
“id”: “78fa590a-3ad1-4b15-ba11-a3921563b3af”,
“name”: “Respond to Webhook”
}
],
“connections”: {},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “e3c1647536678efae553663d350ffe92e3a297c7ca1b2b35540cea551000bc72”
}
}
What are we looking at?
Those are copies of the workflow nodes. A webhook node–>an FTP node–>a response node
Right, let me rephrase… why are we looking at it? 
I apologize, I keep describing what is happening and my posts keep getting hidden?