No Login Fields

[vaughngx4]

**Server Info

• OS: Alma Linux 8.4, Docker version 20.10.14
• Browser: FireDragon, Vivaldi(Chromium), Firefox ESR
• RMM Version (as shown in top left of web UI): v0.12.4

Installation Method:

• Standard
• Docker

Agent Info (please complete the following information):

• Agent version (as shown in the 'Summary' tab of the agent from web UI): v2.0.2
• Agent OS: Win 10 v2004

Describe the bug
Tactical RMM login page has no input fields. Greeted by "TacticalRMM" heading and a login button.

To Reproduce
Steps to reproduce the behavior:

1. Update from v0.12.2
2. Visit Tactical Web UI

Expected behavior
Fields should be shown to login.

Screenshots

Additional context
Apologies if there is some configuration error on my end, I've attempted all I can aside from rolling back to v0.12.2.

[dinger1986]

Have you tried update.sh --force?

[vaughngx4]

Have you tried update.sh --force?

This is a Docker install, is there something in the update script that I should know about in Docker?

Docker update shows to just download new docker-compose.yml

[dinger1986]

Ah sorry, I'll leave that to someone a bit more qualified

[vaughngx4]

Ah sorry, I'll leave that to someone a bit more qualified

No worries.

However, I can confirm that rolling back to v0.12.2 fixes the issue.

[dinger1986]

That's good to know!

I'll ask on discord if any docker wizards can hit you up here.

[silversword411]

You followed this?
https://docs.tacticalrmm.com/update_docker/

Probably best to use discord for troubleshooting.

[vaughngx4]

You followed this? https://docs.tacticalrmm.com/update_docker/

Probably best to use discord for troubleshooting.

Yes I did. Okay, thanks. Will drop by when I have some time.

[wh1te909]

related quasarframework/quasar#13154

[daygle]

Same issue here...

Appears that recent update caused this.

[wh1te909]

I'll do a small release in a couple hours with a fix for this

[wh1te909]

I have reverted the latest stable docker version to 0.12.2 please change it in your .env file and downgrade if you have already updated

[daygle]

Not sure if this matters.

0.12.3 is working for me - only 0.12.4 has the issue.

[wh1te909]

0.12.4. is working now, you can change back to latest

[ninjamonkey198206]

@wh1te909 , I just updated a Docker install using the latest tag and it's not showing a login.

Looks like the same error as your image above.

[wh1te909]

@ninjamonkey198206 with devtools open, right click on the refresh button in chrome > Empty Cache and Hard Reload

[daygle]

0.12.4 is working for me now.

Thanks for your work on this one :)

[ninjamonkey198206]

@wh1te909 I'll give that a shot after I bump back up to 0.12.4

I rolled back to 0.12.2 after posting my comment and screencap.

[vaughngx4]

0.12.4. is working now, you can change back to latest

Can confirm login page is working again. Thanks!

[vaughngx4]

@wh1te909 , I just updated a Docker install using the latest tag and it's not showing a login. Looks like the same error as your image above.
@ninjamonkey198206
If you have been using the latest tag since install you may need to remove existing images before doing a docker pull. You can do this quickly using:

docker rmi $(docker images | grep -o 'tactical-[a-z]*')
docker rmi tactical

[ninjamonkey198206]

@vaughngx4 I always purge old images and unused volumes after updates, and check to ensure the current images are in use. Just part of the update process for me.

Just finished the update, will test.

[ninjamonkey198206]

No joy. Still showing the same error. Completely wiped browser cache for giggles, no change.
Verified new images in use, unused volumes removed. Checked docker-compose file, good.

Edit: Figured it out. Had to completely kill off the old containers and new images, leaving the named volumes in place, then re-pull the new images and start it all up again.

[silversword411]

Had to completely kill off the old containers and new images, leaving the named volumes in place, then re-pull the new images and start it all up again.

As a Docker noob, isn't that what you always have to do for updating docker?

[vaughngx4]

Had to completely kill off the old containers and new images, leaving the named volumes in place, then re-pull the new images and start it all up again.

As a Docker noob, isn't that what you always have to do for updating docker?

Yes. For anyone interested, here is my update script and unattended certificate update(certificates are handled elsewhere and copied to the server via scp).

update.sh

#!/bin/bash
mv docker-compose.yml docker-compose.yml.old
wget https://raw.githubusercontent.com/amidaware/tacticalrmm/master/docker/docker-compose.yml
## Make custom changes to yaml here (I have ports changed)
echo "[BRINGING TACTICAL DOWN...]"
docker-compose down
echo "[REMOVING OLD IMAGES...]"
docker rmi $(docker images | grep -o 'tactical-[a-z]*')
docker rmi tactical
echo "[PULLING NEW IMAGES...]"
cp .env.master .env
docker-compose pull
rm -f .env
echo "[BRINGING TACTICAL UP...]"
./certs.sh

certs.sh

#!/bin/bash
cp .env.master .env
echo "[UPDATING TACTICAL CERTIFICATES...]"
docker-compose down
echo "CERT_PUB_KEY=$(base64 -w 0 ./tactical.fullchain)" >> .env
echo "CERT_PRIV_KEY=$(base64 -w 0 ./tactical.key)" >> .env
docker-compose up -d --remove-orphans
rm -f .env

Where .env.master is simply .env without certificates.

[ninjamonkey198206]

Sort of.

I should probably clarify.

Docker-compose down brought things down, but that didn't fix the issue.

I had to manually stop the containers, remove the containers, remove ALL images related to tactical, then bring it back up.

Docker-compose down, the usual step, wasn't enough.

[ninjamonkey198206]

In other words, I had to manually purge the containers, networks, and images for some reason.

[vaughngx4]

In other words, I had to manually purge the containers, networks, and images for some reason.

It's because 0.12.4 was re-released. There was a buggy version and there is now a fixed version. The tag is the same which is why you had to delete the images(my script above does this regardless).

[vaughngx4]

Sort of.

I should probably clarify.

Docker-compose down brought things down, but that didn't fix the issue.

I had to manually stop the containers, remove the containers, remove ALL images related to tactical, then bring it back up.

Docker-compose down, the usual step, wasn't enough.

docker-compose down should remove containers and networks. I think your issue was simply the re-tagged images.