Skip to content
Webhook Call URL St...
 
Notifications
Clear all

Webhook Call URL Stuck on Localhost

4 Posts
4 Users
0 Reactions
6 Views
Nono_Digital_Assets
(@nono_digital_assets)
Posts: 1
New Member
Topic starter
 

Hello everyone,

I've recently run into a snag with callin.io when setting up the Webhook Call URL in my workflows. The URL seems to be fixed on “localhost,” and I can't seem to change it within the callin.io interface.

Context:

  • I installed callin.io directly on my VPS via Putty, and I access callin.io using my VPS's IP address: http://51.210.242.54:5678/ .
  • When I add a Webhook Call node to my workflows, the URL defaults to “localhost” and is grayed out, preventing any modifications.

I'm facing a similar problem with authentication for some apps like Airtable.

Actions Taken So Far:

  1. I've attempted to remove and re-add the Webhook Call node, but the URL continues to be stuck on “localhost.”
  2. I reviewed the configuration in the ~/.n8n/config file and added the following:
    “tunnel”: {
    “enabled”: false
    }

However, this did not resolve the issue.

Question: Has anyone else encountered this problem, or do you have any suggestions for a solution?

Additional Information:

  • callin.io Version: n8n/1.20.0 linux-x64 node-v18.19.0
  • callin.io Installation Method: Direct installation via Putty

Thank you in advance for your help!

 
Posted : 24/01/2024 9:27 pm
n8n
 n8n
(@n8n)
Posts: 97
Trusted Member
 

It seems your topic is missing some crucial details. Could you please provide the following information, if it applies?

  • callin.io version:
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app):
  • Operating system:
 
Posted : 24/01/2024 9:27 pm
Jon
 Jon
(@jon)
Posts: 96
Trusted Member
 

Hello,

Welcome to the community
:cake:

It appears the missing piece is the WEBHOOK_URL environment variable. I suggest removing the changes you made to the config file and setting the environment variable instead. This should resolve the issue.

 
Posted : 25/01/2024 6:25 pm
system
(@system)
Posts: 332
Reputable Member
 

This thread was automatically closed 90 days following the last response. New replies are no longer permitted.

 
Posted : 24/04/2024 6:25 pm
Share: