Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email Bot Troubles #3364

Open
b-don194 opened this issue Mar 16, 2024 · 1 comment
Open

Email Bot Troubles #3364

b-don194 opened this issue Mar 16, 2024 · 1 comment

Comments

@b-don194
Copy link

This is my first time using Huginn. I'm attempting to set up an email bot for my class project using Gmail as a test platform before I fully integrate it into the rest of the project. Similarly to other users, I was running into the "535-5.7.8 Username and Password not accepted" error and looked at a couple previous posts to try and solve it. I ended up resorting to creating an app password specifically for Huginn and tried to modify the SMTP doman, user_name, and password stored within the .env file in docker. After changing them to the ones I was using as a test, I restarted docker and got and error telling me something along the lines of "chmod. cannot alter the permissions of .env." I am not sure how to alter the SMTP information without breaking the container. If anyone can help with this please let me know. Thanks.

@Forsyth-Creations
Copy link

We were able to resolve this issue on Ubuntu 22 and Windows implementations. I think this line of the README could use more clarity:

* Copy .env.example to .env (cp .env.example .env) and edit .env, at least updating the APP_SECRET_TOKEN variable.

In my head, I would prefer a huginn deployment that uses compose, such as the following:

services:
  huginn:
    image: huginn/huginn
    ports:
      - "3000:3000"
    volumes:
      - .env:/app/.env

However, when sharing the .env file, huginn doesn't like that the system owns it. When I ran this command in Ubuntu I was able to share it through into the container:

sudo chown 1001:0 .env

So when we moved @b-don194 to a Windows system, we used Docker copy to directly inject the new .env file (as I wasn't sure at the time how to change the Windows file permissions. That command was something like the following:

docker cp .env <container_name>:/app/.env

Hope this helps the next person!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants