MeshCentral: Can't download client files from mobile webui
Describe the bug On the mobile version of the webui, it is impossible to download any files from a client. I can’t “click” on the file, nothing happens. Forcing the desktop page in my phone browser solve the problem. It only affect the mobile/phone version of the webui.
To Reproduce Steps to reproduce the behavior: Visit the site with your mobile and try to download a file from one of your client to your phone.
Expected behavior File links should be “clickable” in the mobile version of the webui.
Screenshots
On mobile, can’t click 😦
After forcing the desktop view, it’s all good!
Server Software (please complete the following information):
- OS: Debian 12
- Virtualization: Proxmox LXC
- Network: LAN only
- Version: 1.1.35
- Node: ?? ??
Client Device (please complete the following information):
- Device: Android phone
- OS: Android 14
- Network: Connect to server webui from phone. All on LAN
- Browser: Firefox for Android
- MeshCentralRouter Version: N/A
Remote Device (please complete the following information):
- Device: Desktop
- OS: Latest Windows 10
- Network: LAN
- Current Core Version (if known): Dec 9 2022, 3493876492
Additional context Add any other context about the problem here.
Your config.json file
{
"$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
"__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
"__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
"settings": {
"_cert": "myserver.mydomain.com",
"_WANonly": true,
"LANonly": true,
"FastCert": true,
"_sessionKey": "MyReallySecretPassword1",
"_port": 443,
"_aliasPort": 443,
"_redirPort": 80,
"_redirAliasPort": 80
},
"domains": {
"": {
"_title": "MyServer",
"_title2": "Servername",
"_minify": true,
"_newAccounts": true,
"_userNameIsEmail": true
}
},
"_letsencrypt": {
"__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
"email": "myemail@mydomain.com",
"names": "myserver.mydomain.com",
"skipChallengeVerification": true,
"production": false
}
}
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16
The difference between 1.1.0 and 1.1.35 is 2 years and 816 commits, so it’s going to be hard to narrow down exactly what it is…
But just hang fire, and I’ll have a look tomorrow for you
It will probably be something so simple or so stupid!
Those docs are old and outdated,
I don’t believe it’s an option anymoreI stand corrected, the option
fastcertis still uses but not recommended as its only rsa2048 and everyone is moving to rsa3072