mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #349] Bad Credential after completing Dockerized new install with default and/or custom creds #220
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#220
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wiicode on GitHub (Mar 29, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/349
Server Info (please complete the following information):
Installation Method:
Describe the bug
Followed installation process for Docker. Attempted with only necessary mods to .env and extended ones. Necessary mods were just certs and DNS. Extended mods were all new user names and passwords.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected to be able to access login page and login with tactical/tactical or using my custom creds.
However, both threw "Bad Credentials"
Additional context
My install is scripted via https://github.com/wiicode/automation-scripts/blob/main/tacticalrmm/install_tacticalRMM_on_AWS_Ubuntu_20.sh
@wh1te909 commented on GitHub (Mar 29, 2021):
Hi please see this https://wh1te909.github.io/tacticalrmm/troubleshooting/#bad-credentials-error-when-trying-to-login-to-the-web-ui check your dns and port forwarding
I'll test your install script tmrw on AWS to see if can reproduce
@wiicode commented on GitHub (Mar 29, 2021):
I am sorry, I was being dense. I thought I had resolved the cert issue
earlier, I had not. It's most def a cert issue because I ended up issuing
a cert for my APP_HOST domain only.
On Mon, Mar 29, 2021 at 6:03 AM Dan @.***> wrote:
@dinger1986 commented on GitHub (Apr 11, 2021):
Shall close this as sounds like its working