[GH-ISSUE #1485] New install can't access tactical url but can access mesh url #2873

Closed
opened 2026-03-14 05:46:43 +03:00 by kerem · 4 comments
Owner

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.

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.
kerem closed this issue 2026-03-14 05:46:48 +03:00
Author
Owner

@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.

<!-- gh-comment-id:1510379052 --> @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.
Author
Owner

@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

<!-- gh-comment-id:1510379374 --> @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
Author
Owner

@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.

<!-- gh-comment-id:1510382305 --> @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.
Author
Owner

@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

<!-- gh-comment-id:1510436570 --> @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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#2873
No description provided.