Benny Tops
Benny Tops
Yep. Just add it to docker-compose.override.private.yml. Something like: ``` n8n: ports: - 127.0.0.1:5678:5678 environment: - N8N_SECURE_COOKIE=false ``` That should fix it.
For the 2 endpoints without authentication (ollama and searxng) we could add Caddy configuration to add at least basic authentication, then we can uncomment them (username + password in .env)....
And if you like, I can continue my quest for more security with Docker capabilities, setting a user, etc. Basically, checking the boxes of https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html
@leex279 Yes, I have commented out 2 endpoints, because they are without authentication. People are deploying this to the public cloud like DigitalOcean as shown in one of the videos!...
@leex279 If we configure basic_auth, we should also add rate limiting to mitigate brute force attacks ...
I couldn't agree more.
I'll post testing proof this evening.