mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1485] New install can't access tactical url but can access mesh url #2873
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#2873
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 @ioscanner on GitHub (Apr 16, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1485
I did a first time new install. Everything seemed to go ok. Them went to connect to the tactical url and it doesn't show up. The mesh url works.
I am not sure what version of tactical it is, but the mesh is 1.1.5 in the interface.
Installed on Debian 11. Single IP with DNS for mesh and tac urls.
Installation Method: Standard
I can get there by IP it seems, but when I try to login it tells me the backend is down. The nginx file looks correct.
@ioscanner commented on GitHub (Apr 16, 2023):
I got it. Seems the host file after install was wrong. You put 127.0.0.1 tactical.server tac api.server mesh.server
Split them into
127.0.0.1 tactical.server tac
127.0.0.1 tapi.server tapi
127.0.0.1 mesh.server.com mash
Seems it is a bug in the installer.
@dinger1986 commented on GitHub (Apr 16, 2023):
It's always worked fine for me and I have done installs probably in the 3 figures now
@ioscanner commented on GitHub (Apr 16, 2023):
Just reporting what I found. I was able to resolve it. When I install the other location I will report if it does it again. I did see someone else said something about the host file needing to be updated. So maybe a patch broke it.
@silversword411 commented on GitHub (Apr 16, 2023):
Your problem is probably using AWS and it breaking network settings and cloudinit
https://docs.tacticalrmm.com/troubleshooting/#issues-with-agents-offline-after-reboot-or-new-install-on-aws-and-other-cloud-platforms-using-cloudinit-or-similar