Open cjyoung55 opened 11 months ago
closed.
closed.
What did you change to fix this?
Was not able to fix this. I ended up using meshcentral without docker and its working. Not sure why I couldn't use an older version using the docker image.
I'm having the same issue. Has anyone found a fix for the docker version?
Is this still happening?
Having trouble using latest version 1.1.10. Blank screen problem when connecting to any client. Trying to downgrade to stable version 1.1.0 via docker-compose.yml as well. But it still downloads latest version 1.1.10.
My docker-compose specified "image: typhonragewind/meshcentral:1.1.0" but it loads 1.1.10 instead. So I tried to downgrade from the meshcentral console and you can see that it did "Starting self upgrade to: 1.1.0" but then shows that its running v1.1.10 and I still have the blank screen problem.
Portainer log follows:
Installing nodemailer... Installing otplib@10.2.3... Installing image-size... Installing archiver@5.3.1... MeshCentral HTTP redirection server running on port 80. MeshCentral v1.1.10, Hybrid (LAN + WAN) mode, Production mode. MeshCentral Intel(R) AMT server running on www.myweb.com:4433. MeshCentral HTTPS server running on www.myweb.com:443. Loaded web certificate from "https://www.myweb.com:443/", host: "www.myweb.com" SHA384 cert hash: b6160ab7c989646ed2f74f733970eb32e5c47029ea912d10df2cdee3df91d8e8559272ee40f8494d5d568da85d4bd8d9 SHA384 key hash: 4a101ea0f1533f4b78eaf0f42d3efd1a6688762ceb0211afc2b5d14bfa8919972f998688992f34aa7aeade3a3100c3ce SMTP mail server smtp.gmail.com working as expected. Starting self upgrade to: 1.1.0 Update completed... Installing archiver@5.3.1... MeshCentral HTTP redirection server running on port 80. MeshCentral v1.1.10, Hybrid (LAN + WAN) mode, Production mode. MeshCentral Intel(R) AMT server running on www.myweb.com:4433. MeshCentral HTTPS server running on www.myweb.com:443. Loaded web certificate from "https://www.myweb.com:443/", host: "www.myweb.com" SHA384 cert hash: b6160ab7c989646ed2f74f733970eb32e5c47029ea912d10df2cdee3df91d8e8559272ee40f8494d5d568da85d4bd8d9 SHA384 key hash: 4a101ea0f1533f4b78eaf0f42d3efd1a6688762ceb0211afc2b5d14bfa8919972f998688992f34aa7aeade3a3100c3ce SMTP mail server smtp.gmail.com working as expected.