enduluc
enduluc
hi @cedricve Version 3.1.8 I even reinstall everything, install new ones, and in one case, started working again, but when I restart the container, stopped ....The thing is that I...
hi @cedricve any updates? do you need more information about this, logs, or anything else? I even install one agent in another environment, same results. The agent doesnt recognize the...
Hi @cedricve I have an update. I tested two agents with different url endpoints (condition url). Those endpoints are in my nodered instance. The results: http://192.168.192.30:1880/endpoint ----> this always works...
Hi @cedricve, any updates?
Hi @cedricve any updates? I ran some test and find out that kerberos only works with nodered home assistant addon. When i recreate the same flow in a nodered vm...
Hi @cedricve, is me again. Just to know if there is light at the end of the tunnel. Im running a bunch of tests, with different node-red instances (lxc, docker,...
Hi @cedricve I hope you are doing well. Have you had the oportunity to check this bug?
ok, lets recapitulate: agent and nodered installed in docker, same network inside agent sh **~ $ curl -i http://172.16.0.20:1880/endpoint HTTP/1.1 200 OK Access-Control-Allow-Origin: * X-Content-Type-Options: nosniff Content-Type: application/json; charset=utf-8 Content-Length:...
any thoughts ??? @cedricve @andp97
I fixed the 301. I test it within the sh container and the browser, got the 200. But still, not working. Easy way to replicate this: Install kerberos agent on...