You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system: Docker on Windows, Linux Container monitorr/monitorr
Webserver: NGINX 1.12.2
PHP Version: 7.1.17
Monitorr Version: 1.7.6m
Describe your issue:
Looks like the images don't handle uppercase. There is a built-in image qBittorrent.png. I added a qBittorrent service and used that image. When I go to the homepage, it shows a broken image. Inspecting that image shows "qbittorrent.png". If I change it to "qBittorrent.png" it shows up. The services_settings-data.json file has it correct, "qBittorrent.png" but when it gets sent to the browser, it gets sent as "qbittorrent.png".
@vinaykapadia This is interesting and I thought we had addressed it a while back in an update.
What browser are you using? I've tested on Chrome and Firefox (on Windows 10) and the default image is displayed despite the case of the filename in the services_settings-data.json file or the actual filename on the web server.
I was actually having the same issue. Running it on Docker on latest dev. I uploaded the qBit file myself in order to get around the issue. Browser was Firefox in my case.
Your environment:
Operating system: Docker on Windows, Linux Container monitorr/monitorr
Webserver: NGINX 1.12.2
PHP Version: 7.1.17
Monitorr Version: 1.7.6m
Describe your issue:
Looks like the images don't handle uppercase. There is a built-in image qBittorrent.png. I added a qBittorrent service and used that image. When I go to the homepage, it shows a broken image. Inspecting that image shows "qbittorrent.png". If I change it to "qBittorrent.png" it shows up. The services_settings-data.json file has it correct, "qBittorrent.png" but when it gets sent to the browser, it gets sent as "qbittorrent.png".
I have read the t-shooting Wiki at: https://github.com/Monitorr/Monitorr/wiki/06-Troubleshooting
The text was updated successfully, but these errors were encountered: