I have been setup the instance myself and I was the first user to login into the application but I don't seem to see the super admin account where I can configure email server
#How can I find my super admin account in appsmith-ce?
covert plinth
errant ruinBOT
Hello! I'm AppySmith, your support bot for all things Appsmith. Let's tackle the
issue you’re facing. In Appsmith, the first user to sign up on a new self-hosted
instance is automatically assigned the superuser role, which includes admin
privileges. If you were the first user, your account should indeed have
superuser access. To configure the email server, you need to access the admin
settings within the Appsmith interface. Please follow these steps: - Log in to
your Appsmith instance. - Click on the profile icon in the top right corner. -
From the dropdown menu, select 'Admin Settings'. - Navigate to the 'Email' tab
where you can configure the email server settings. If for some reason you're not
seeing the 'Admin Settings' option, it's possible that there might have been an
issue with the setup. In that case, could you let me know if you are seeing any
error messages or specific issues, and also provide me with the deployment
method you used? This will help me give you more accurate instructions. If you
don't find my response helpful, you can request to speak to a human agent
covert plinth
I was the first user but it didn't seem to work. I've followed the docker installation guide mentioned on Appsmith docs
errant ruinBOT
Understood, let's try to troubleshoot this. Since you followed the Docker
installation guide, there are a few checks we need to perform. Before we proceed
further, could you confirm if your instance is up and running without other
issues, and are able to log in with your user account? Also, are you comfortable
with running Docker commands to check the status of your containers? This
information will help me guide you in the right direction. If you don't find my
response helpful, you can request to speak to a human agent
errant ruinBOT
Great, thanks for confirming that. Let's move forward with the next steps. Since
you used Docker Compose and your instance is up and running, we need to check if
the environment configurations were set correctly, which might affect the admin
settings visibility. Perform the following steps: - SSH into your EC2 instance
where Appsmith is running. - Navigate to the location where you have your
docker-compose.yml and stacks/configuration/docker.env files. - Open the
docker.env file to ensure that the APPSMITH_MAIL_ENABLED is set to true, which
would look something like this: APPSMITH_MAIL_ENABLED=true. If
APPSMITH_MAIL_ENABLED is not set to true, or if the variable is missing: - Set
the variable to true: APPSMITH_MAIL_ENABLED=true. - Save the file. - Restart
the Appsmith services by running: docker-compose restart. Please try the above
steps first and see if this resolves the issue. If not, we may need to inspect
the logs for your Appsmith server container to see if there are any apparent
issues with the initial setup or permissions. You can view logs using the
command: docker-compose logs -f appsmith. Let me know how this goes, or if you
encounter any errors during the process. If you don't find my response helpful,
you can request to speak to a human agent
covert plinth
Do I neeed to update any other env varibale?
errant ruinBOT
For setting up the email service, apart from enabling it with
APPSMITH_MAIL_ENABLED=true, you'll also need to configure the specific email
variables to connect to your email server. Here are the variables you should
provide values for in your docker.env file: - APPSMITH_MAIL_FROM: The email
address from which emails will be sent. - APPSMITH_REPLY_TO: The email address
to which replies to Appsmith emails will go. - APPSMITH_MAIL_HOST: The SMTP
host for the email service (for example, smtp.gmail.com for Gmail). -
APPSMITH_MAIL_PORT: The SMTP port (typically 587 for TLS). -
APPSMITH_MAIL_USERNAME: The username for your email service. -
APPSMITH_MAIL_PASSWORD: The password for your email service. -
APPSMITH_MAIL_SMTP_AUTH: Usually set to "true"; indicates that authentication
is required. - APPSMITH_MAIL_SMTP_TLS_ENABLED: Set to "true" if your email
service uses TLS. - APPSMITH_MAIL_SMTP_SSL_ENABLED: Set to "true" if your
email service requires SSL encryption. - APPSMITH_MAIL_SMTP_TLS_TRUST: If
needed, provide a space-separated list of hosts that are trusted for TLS (use
this cautiously). These additional variables must be set correctly for Appsmith
to be able to send emails. Make sure to replace these placeholders with your
actual email service provider's details. After updating and saving the
docker.env file with these variables, you will need to restart the Appsmith
services for the changes to take effect: sh docker-compose down docker-compose up -d Running these commands will restart the services
defined in your docker-compose.yml file with the new environment
configurations. Once you have made these changes, log into Appsmith, and the
'Admin Settings' option should be visibly updated to reflect your configuration.
Let me know if you need further assistance or if something is not working as
expected. If you don't find my response helpful, you can request to speak to a
human agent
errant ruinBOT
Could you please share a screenshot of your dashboard after you log in with the
instance admin user? Are you not able to see the Admin Settings?
covert plinth
I don't have a SMTP is it mandatory?
errant ruinBOT
To send emails from Appsmith, such as for inviting users, password resets, or
for workflow notifications, an SMTP server is required. Appsmith doesn't provide
an inbuilt email service; instead, it relies on an external SMTP server to send
emails. If you don't have an SMTP server, you will need to use a third-party
SMTP service provider. Many email services like Gmail, Office 365, SendGrid,
Amazon SES, and others provide SMTP service which you can configure with
Appsmith. Each service typically offers a free tier with limitations on the
number of emails that can be sent daily or monthly. Remember to consider the
security and privacy implications of the email provider you select, especially
if you are dealing with sensitive information. Should you need assistance in
choosing an SMTP service or require further clarification, feel free to ask. If
you don't find my response helpful, you can request to speak to a human agent