Blocked GET /workflow/etc

Questions
1

I’ve been seeing lots of this in my logs recently, that I have never seen before, anyone else noticed similar? Or is there some misconfiguration that has snuck in somewhere?

Blocked GET /workflow/xxxxxx1 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx2 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx3 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx4 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx5 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx6 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx7 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx8 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx9 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx10 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx11 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx12 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx13 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx14 for "TelegramBot (like TwitterBot)"
Blocked GET /workflow/xxxxxx15 for "TelegramBot (like TwitterBot)"
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey @RedPacketSec,

Does it show anything else? Is it specific to a version you are running maybe? and I guess which log are you seeing that in?

4

Nope just shows those in-between other logs.

This is from the docker console logs.

Im using the AI beta

5

That is interesting, I have not seen that before. Which version of n8n is your ai-beta version using? We update the same image so you could be an old version or a newer version.

6

My docker is set to latest .

So each day it checks and updates to most recent

7

Ah my mistake I thought you were using ai-beta as the image not latest.

8

yeah, using ai-beta (latest version)

9

Hey @RedPacketSec,

Can you confirm what the latest version is that you are using? We update the same tag so unless you are pulling the same image every night you could be on one of a few different versions. My ai-beta version on my self hosted install is currently built on 1.18.0

10

n8n Version

1.18.0

11

Perfect, So it won’t help but I have checked my log and I am not seeing the same messages so I think more information could be needed. It sounds like something or someone is trying to load the workflow though.

12

Hi folks, n8n is blocking bot requests to certain URLs since version 1.6.0: fix(core): Prevent bots from scanning the application (no-changelog) by netroy · Pull Request #7066 · n8n-io/n8n · GitHub

So this is expected when using services such as Telegram or Slack that might try to automatically access a URL shared in a chat to generate a preview (which would fail anyway for n8n as these URLs require a login).

I am not sure if this should be logged as INFO though. @netroy would it perhaps make sense to lower the logging level for these messages?

2 Likes
13

Of course, I missed that bit at the end :man_facepalming:

14

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