Closed heywiorld closed 2 years ago
Hey @heywiorld,
I believe that could be the Telemetry data failing to send, it is not anything anything to worry about and is potentially to be expected if you are on an internal private network with outbound network calls restricted.
You can try setting N8N_DIAGNOSTICS_ENABLED
to false if you want to disable it.
but always see error in log:
@heywiorld,
That looks like it is someone trying to log in or acces something they don't have access to.
@heywiorld,
That looks like it is someone trying to log in or acces something they don't have access to.
yeah, but no more details, so I don't know where is the error
Hey @heywiorld,
Is your instance available to the internet or are you doing any service checks to make sure it is online?
Depending on your setup it could be a few things but I can't think of anything that would be an issue with n8n itself.
If you are using a reverse proxy you could check the logs there to see if that shows where the connection is coming from and what url it is trying to access. If there is nothing in those logs it would be something that isn't using the reverse proxy and something that is able to connect directly.
ok. will check reverse proxy log, thanks
@heywiorld Could you solve it? It's giving me the same problem
Describe the bug found rudder error when using docker N8N
To Reproduce Steps to reproduce the behavior:
Expected behavior no error.
Environment (please complete the following information):
own
]Additional context